Repository navigation
Rely on native JSON handling to format the callsigns - #7
Open
darryldunkin wants to merge 2 commits into
Open
darryldunkin wants to merge 2 commits into
darryldunkin wants to merge 2 commits into
Conversation
… of call signs as a vec/array natively. This prevents the import from becoming a single string of callsigns with commas, to individual elements.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is not my natural language, so some changes may be inappropriate.
Whenever I use the tool, Hamalert prints out the callsigns as a single callsign instead of a list. If I open the cli-generated list and 'save', the web UI will break it apart into individual callsigns again. This screenshot shows the difference between the two.

The changes included remove all of the formatting and leaning on json itself to handle the objects natively.