Skip to content

Conversation

berkerozer
Copy link

🐛 Fix: Register Conflict Between @blockly/field-grid-dropdown and @blockly/field-colour

This PR addresses an issue where using @blockly/field-grid-dropdown and @blockly/field-colour together would cause a Name "field_grid_dropdown" already registered error due to double registration.

🔧 Changes Made

  • Introduced a new utility function registerFieldGridDropdown() in @blockly/field-grid-dropdown.
  • Modified @blockly/field-colour to import and call registerFieldGridDropdown() explicitly.
  • Ensured that the dropdown field is only registered once and safely when needed.

✅ Benefits

  • Avoids duplicate field registration errors.
  • Improves modular use of Blockly plugins.
  • Safer integration of multiple plugins across different projects.
Ekran Resmi 2025-09-07 01 47 13

@berkerozer berkerozer requested a review from a team as a code owner September 6, 2025 22:48
@berkerozer berkerozer requested review from cpcallen and removed request for a team September 6, 2025 22:48
Copy link

google-cla bot commented Sep 6, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@berkerozer berkerozer force-pushed the berkerozer/field-dropdown-registration branch from b7e3cdb to c8a9d51 Compare September 6, 2025 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants