Added the possibility to have custom parsers#41
Open
AFASbart wants to merge 1 commit intoeealeivan:masterfrom
Open
Added the possibility to have custom parsers#41AFASbart wants to merge 1 commit intoeealeivan:masterfrom
AFASbart wants to merge 1 commit intoeealeivan:masterfrom
Conversation
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
1 participant
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.
When creating track messages a parser is used by this package that can only handle a very limited number of property types. We at AFAS want to use a more complex parser to send our messages. I saw an issue where someone else also wants to have this.
I would recommend to implement this in this way so that this package stays simple and generic, and for the more advanced users we can create our own (specialised) parsers.