Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Path::parse vs Path::of #18

Open
frankwis opened this issue Mar 7, 2017 · 0 comments
Open

Path::parse vs Path::of #18

frankwis opened this issue Mar 7, 2017 · 0 comments
Labels
bug help wanted

Comments

@frankwis
Copy link
Member

frankwis commented Mar 7, 2017

Handling of parse and of is confusing since both take string arguments, but behave differently:

Path.of("/com")

results in

io.datanerds.avropatch.exception.InvalidReferenceTokenException: /com is not a valid JSON path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@frankwis