You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for similar issues before opening a new one.
Component
Angle, colour, and multiline input fields.
Description
After #2162 there will be multiple pieces of code in field plugins that compensate for the blocks and fields already being installed as part of the core library. Once the fields are removed form core (google/blockly#7226), the plugins will need to be updated.
Examples include
In test pages, deleting blocks and generators for blocks provided by the plugin.
In field registration functions, unregistering existing fields before registering the new ones.
Reproduction steps
No response
Stack trace
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Is this release blocking? If so, might be good to bump the priority. I think we might not get to some of the P1s this Q, and I don't want this to get lost.
No, this isn't release blocking. These are only changes in samples, and the existing code will not break when the fields are deleted from core--it'll just be useless clutter.
Check for duplicates
Component
Angle, colour, and multiline input fields.
Description
After #2162 there will be multiple pieces of code in field plugins that compensate for the blocks and fields already being installed as part of the core library. Once the fields are removed form core (google/blockly#7226), the plugins will need to be updated.
Examples include
Reproduction steps
No response
Stack trace
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: