Open
Conversation
|
@WeiKian did you find a workaround for this? |
Author
|
@mwilliams1188 Yup. Fork it and update the odata-v4-parser dependencies will do the trick. |
|
Thank you @WeiKian. This may be a dumb question but did you have to redeploy as an npm package or did you just use it some other way. |
Author
|
@mwilliams1188 Yeah I did republished so that I'm able to use it but I don't know if this is allowed haha. If the author merge this then I will unpublish it >.< |
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
2 participants
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.
The parser version used is not up to date and caused unexpected character error while there's nothing wrong with the odata syntax. Update the version fixed the issue.