You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a very basic reference implementation that I can compare my library’s output against would make fuzzing out bugs and corner cases much easier. It probably makes sense to output data in something easy to work with on the CLI, maybe a tab-delimited file similar to the FitToCSV tool output.
The text was updated successfully, but these errors were encountered:
stadelmanma
changed the title
Create a reference implantation using Fit SDK java library for testing
Create a reference implementation using Fit SDK java library for testing
Dec 8, 2022
stadelmanma
changed the title
Create a reference implementation using Fit SDK java library for testing
Create a reference implementation using Fit SDK library for validation
Feb 7, 2023
The CPP code looks like a good start for this. Yeah We’ll want to track the message name & number, and then inside that the field name, number, value and type.
Whatever format the implementation creates we’ll need it to be:
easy to read
easy to view a diff of (e.g. using git diff)
simple to generate (no extra libs needed)
easy to parse
The first two reqs mean we will want to keep line lengths reasonable which excludes JSON lines. True JSON is also not exceptionally easy to parse or generate without pulling in extra libraries anyways. For parsing ease we want to avoid multiple spaces as a delimiter; single tabs and and new lines are fine.
A basic indented structure comes to mind:
HEADER
:TAB:header field
…
MesgNum,Message Name
:TAB:FieldNum,FieldName,FieldType,Value
…
…
Having a very basic reference implementation that I can compare my library’s output against would make fuzzing out bugs and corner cases much easier. It probably makes sense to output data in something easy to work with on the CLI, maybe a tab-delimited file similar to the FitToCSV tool output.
The text was updated successfully, but these errors were encountered: