URCA CAN Tooling ✨ #176
Draft
URCA CAN Tooling ✨ #176
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
dchansen06
added
Documentation
dchansen06
added
the
1 URGENT
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
URCA Can Tooler
Problem and Scope
Last year CAN ID updating very painful and sad -- manual downloading/parsing of google sheet per change.
Description
ID Constants to autogenerate header files upon compile from custom yaml format to enums/structs/as needed.
Gotchas and Limitations
No nice UI, single raw huge yaml file. Other stuff.
Testing
Lots of it. Error handling for all incorrect input, testing with last year's data spreadsheet
Testing Details
Yes
Larger Impact
Reduce data->code conversion errors, less manual human labor & upkeep needed to manage IDs.
Additional Context and Ticket