-
Notifications
You must be signed in to change notification settings - Fork 8
Pr test print #161
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
Pr test print #161
Conversation
(annotations are something different in python)
* toolbox. | ||
*/ | ||
export const mechanism_class_blocks: toolboxItems.Block[] = [ | ||
{ |
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.
Why are these hardcoded? Can't we generate these blocks from json?
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.
I just kept them like they were before. I don’t see any reason they can’t be json
export const robot_class_blocks: toolboxItems.Block[] = [ | ||
// TODO(lizlooney): Add one mrc_class_method_def blocks for each method in ther Robot class. | ||
]; | ||
{ |
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.
Why are these hardcoded? Can't we generate these blocks from json?
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.
Made them the same as the ones for opmode and mechanism. I don’t see a reason they couldn’t be json.
This includes all code to run our blockly code!!!
(I apologize for doing some other cleanup at the same time)
Changes to base classes as well as our code generator.
This only tests opmode and robot classes. It does not test mechanism generation.