Skip to content
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

fix: decoder handle compressed timestamp for unknown field #246

Merged

Conversation

muktihari
Copy link
Owner

When encountering compressed timestamp message but the message is unknown (it could be manufacturer specific message), the field become unknown as well, in such cases, we must assign the BaseType and Type to uint32 so that the resulting decoded FIT can be encoded as per original instead of returning error in encoder since the BaseType was set to default value: Enum.

@muktihari muktihari self-assigned this May 10, 2024
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ac559cb) to head (bb5af8e).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #246   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           42        42           
  Lines         3615      3618    +3     
=========================================
+ Hits          3615      3618    +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@muktihari muktihari added the bug Something isn't working label May 10, 2024
@muktihari muktihari merged commit 7990387 into master May 10, 2024
4 checks passed
@muktihari muktihari deleted the fix/decoder-handle-compressed-timestamp-unknown-field branch May 10, 2024 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants