This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
Fix quoting issue in search_operator plugin #3479
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Mar 2, 2023
Glandos
reviewed
Apr 2, 2023
|
Thanks for looking into this issue. Do you mind fixing the error reported by the linter? |
glanham-jr
force-pushed
the
fix-search-operator-quote
branch
from
8253d55
to
acce623
Compare
Fixed |
kvch
approved these changes
Apr 5, 2023
|
Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fix the apostrophe issue described in #3414 (read diagnosis there) by using
shlex.quote.Why is this change important?
Fixes a 500 Server Error issue when Search Operator is being used with apostrophes.
How to test this PR locally?
Author's checklist
Related issues
Closes #3414