New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Location variables #23204
Location variables #23204
Conversation
[Blockly.BlockValueType.LOCATION]: [block.getTitleValue(inputConfig.name)], | ||
}; | ||
}; | ||
block.renameVar = function (oldName, newName) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can some of these inherit from Blockly.Blocks.variables_get
?
"args": [ | ||
{ | ||
"name": "VAR", | ||
"assignment": true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Tempting to make this a separate field instead of part of "args", but it makes sense that these get populated from the block inputs, in order. If we could start over, maybe these would be called "fields" instead of "args"?
How does a level builder add the "Locations" custom category? Do we need to add an entry to the list in PR #23198? |
You may also want the That said, we prob don't care about renaming vars in the preview Block Space. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
None of this feedback should be blocking... good to merge as-is.
222c048
to
62be0b1
Compare
62be0b1
to
13892da
Compare
No description provided.