-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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: encode rison characters when searching #16768
Conversation
abf110f
to
d78a083
Compare
Codecov Report
@@ Coverage Diff @@
## master #16768 +/- ##
==========================================
- Coverage 76.99% 76.74% -0.25%
==========================================
Files 1007 1007
Lines 54133 54186 +53
Branches 7374 7464 +90
==========================================
- Hits 41678 41584 -94
- Misses 12215 12362 +147
Partials 240 240
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
d78a083
to
3c0aa22
Compare
3c0aa22
to
2b01a95
Compare
@betodealmeida |
Related: #18056 |
SUMMARY
When searching for charts/dashboards/datasets we're currently getting an error if the needle has a plus symbol, eg,
/w+
. This happens because the+
is not escaped, and gets sent as a space to the backend. Because the string/w
is not valid rison, the search fails.I fixed by explicitly encoding
+
. We could useencodeURIComponent
, but it encodes more than is needed and pollutes the URL.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
After:
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION