-
Notifications
You must be signed in to change notification settings - Fork 1
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
Revamp yaml structure slightly #126
Conversation
Additional changes
Additional verifications with this change
See the README for the list of limitations in writing CAN messages. The biggest issue right now is signed messages must be full bytes, but tbh thats how everyone should be doing it imo. |
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 mean if it works it works. I personally feel like there must be a way to not have wrappers. But ig there was a reason i did it like that in the first place 🤷
get rid of comment of removed field
Reorganizes some of the yaml structure. Decoding only, I havent tested encoding.
List of changes:
Reasons this may not be usable
points: -!CANPoint
)Things to add in future PRs, if this gets merged
topic_append
in the CANPoint, so as many things can be appending as needed instead of only one at the very beginningsend
in the CANPoint, so you can not send part of messages of 1+ points