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.

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

Node is no longer public in jsonpath-lib 0.2.4 #36

Open
EliSnow opened this issue Feb 19, 2020 · 4 comments
Open

Node is no longer public in jsonpath-lib 0.2.4 #36

EliSnow opened this issue Feb 19, 2020 · 4 comments

Comments

@EliSnow
Copy link

EliSnow commented Feb 19, 2020

In v0.2.3 Node was public, but is no longer exposed.

Unfortunately this breaks code in a semver incompatible way.

I'm using Parser::compile directly and need to store the returned Node. Parser is still exposed but not Node

@freestrings
Copy link
Owner

@EliSnow jsonpath-rs 0.2.4 has been unpublished.
The jsonpath-rs module has been removed from this repository and will be managed by another repository.

@EliSnow EliSnow changed the title Node is no longer public in jsonpath-rs 0.2.4 Node is no longer public in jsonpath-lib 0.2.4 Feb 24, 2020
@EliSnow
Copy link
Author

EliSnow commented Feb 24, 2020

crates.io is still showing 0.2.4. Sorry for the confusion in the title, I actually meant jsonpath-lib the rust library, not the npmjs package. What is the new repository for this library?

@EliSnow
Copy link
Author

EliSnow commented Jan 22, 2021

I just tried out v0.2.6 and Node is still private when it was public in v0.2.3.

@tkmcmaster
Copy link

I just checked v0.3.0 and it looks like Node is still private. Is there any plans to make it public again? We're still currently locked to v0.2.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants