fixed parsing failure when additional spaces occur before semicolon #51
Conversation
This file contains 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
|
@Whitehouse112, please review this contribution. A |
|
@Puchaczov thanks for spot the issue and fix it. It will be merged for the next release Regards |
|
Thank you guys for the library, it is super usefull :-) |
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.
when VAL_ or VAL_TABLE_ finish with semicolon that is prefixed by multiple spaces (3 in my case), then the
ExtensionsAndHelpers.ToDictionaryrecords variable will hold\r\n(there is space after). This causes the tokens will be an array of two items with values of string.Empty for both. This causing int.Parse to fail.I've fixed that so it won't occur anymore.