handling special bearing format + lower/upper casing + tests on invalid input #7513
+149
−42
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.
#7489
In addition addressing casing and special strings, I added tests for out-of-bound numbers/possible invalid inputs.
Couple observations:
these work as treating the missing sections as 00
4, allows numbers bigger than 90 to occur (tests added in this pr)
The parseAndProcessTokens implementation is relatively loose, which seems acceptable to me. Let me know if any behavior is unexpected.