-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check for invalid paths #219
Comments
I would probably suggest we deprecate our path notation (which is built around our random thing) and use a third party library like jsonpath. Only issue is its almost 7000 lines, so might be just add an option in V4 to allow custom JSON path libraries. This would need to be used in both the server and JS, but the server can easily take the extra 80kb weight as a dependency. |
Yeah I’m still 100% for getting rid of our custom paths and using an actual json path implementation. raising this as a V5 issue |
Closing in favour of deepstreamIO/deepstream.io#1046 |
Breaking out from #214.
Json paths should be checked for validity. Currently the behaviour for invalid paths is pretty much undefined.
The text was updated successfully, but these errors were encountered: