Fix load_object color refresh on MODELS change#361
Merged
tracygardner merged 1 commit intomainfrom Mar 8, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
load_objectblock did not immediately update the connectedCOLORshadow/input to the default fromobjectColours, breaking the expected live-update behavior when swapping items.Description
onChangecheck inblocks/models.jsto callupdateColorField()when theMODELSfield changes on theload_objectblock so the connectedCOLORvalue is refreshed from the config immediately.Testing
npm run build, which completed successfully (Vite emitted non-blocking warnings about chunking/externalized modules but the build finished).Codex Task