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

fix: unescape json path properly #458

Merged
merged 2 commits into from
Aug 19, 2019
Merged

fix: unescape json path properly #458

merged 2 commits into from
Aug 19, 2019

Conversation

P0lip
Copy link
Contributor

@P0lip P0lip commented Aug 18, 2019

Fixes #457

Checklist

  • Tests added / updated
  • Docs added / updated

Does this PR introduce a breaking change?

  • Yes
  • No

See the issue for more info. The issue itself is fairly subtle and minor, but it's something that might introduce confusion when the linted document is huge.

@P0lip P0lip requested review from philsturgeon and marbemac August 18, 2019 20:50
@P0lip P0lip self-assigned this Aug 18, 2019
@P0lip P0lip added this to the September '19 milestone Aug 18, 2019
@P0lip P0lip added the t/bug Something isn't working label Aug 18, 2019
@P0lip P0lip merged commit 2bb80b0 into develop Aug 19, 2019
@P0lip P0lip deleted the fix/escape-path branch August 19, 2019 13:31
philsturgeon pushed a commit that referenced this pull request Aug 22, 2019
P0lip added a commit that referenced this pull request Aug 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ranges for JSON paths with escaped slashes are incorrect
2 participants