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

Use new safe_to_set/safe_to_remove functions #3722

Merged
merged 4 commits into from
Feb 29, 2024
Merged

Conversation

xzfc
Copy link
Contributor

@xzfc xzfc commented Feb 29, 2024

This PR is based on #3709.

All Submissions:

  • Contributions should target the dev branch. Did you create your branch from dev?
  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

  1. Does your submission pass tests?
  2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
  3. Have you checked your code using cargo clippy --all --all-features command?

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you successfully ran tests with your changes locally?

@generall generall merged commit 4d545bb into dev Feb 29, 2024
17 checks passed
@generall generall deleted the json-path-safe-to-set branch February 29, 2024 16:09
timvisee pushed a commit that referenced this pull request Mar 5, 2024
* Switch to JsonPathV2

* Use new safe_to_set/safe_to_remove functions, fix PayloadIndex::assign

* minor review fixes

* Rename and inverse

---------

Co-authored-by: generall <andrey@vasnetsov.com>
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

Successfully merging this pull request may close these issues.

None yet

2 participants