-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add Label 22 Takeoff Report #180
Conversation
makrsmark
commented
Oct 29, 2024
- renamed Label_22 to Label_22_POS and added preambles
- renamed Label_22 to Label_22_POS and added preambles
expect(decodeResult.formatted.items[3].label).toBe('Message Timestamp'); | ||
expect(decodeResult.formatted.items[3].value).toBe('17:12:00'); |
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.
this is a little weird, but what I'm calling the timestamp has minute resolution, but the actual takeoff time has second resolution. Open to ideas
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 would say that as long as the raw value is still defined with seconds, the formatted can be whatever.
expect(decodeResult.formatted.items[3].label).toBe('Message Timestamp'); | ||
expect(decodeResult.formatted.items[3].value).toBe('11:52:00'); |
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.
in this variant, both the timestamp and takeoff time have minute resolution - i could be parsing backwards but it probably doesn't matter
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.
LGTM!