plugin.lapce.dev does not handle urlencode properly
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No file or test is named. Start by tracing the plugin search page's query-string handling for an F# search and for manually entered F%23; done means the URL encodes the query correctly and the page displays the decoded search value.
Written by the indexing model from the issue text.
Description
For example, I want to search plugin for F# language, but when I type in "F#" and search, the URL is not properly encoded into F%23, thus it return all results with letter F. If I manually type in F%23 in the address bar, the search input on the webpage does not correctly decodes URL to show F# instead of plain F%23
- Dominant language
- HTML
- Stars
- 14
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lapce/lapce.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
lapce/lapce.github.io#76 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
lapce/lapce.github.io#73 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
lapce/lapce.github.io#24 · 4 comments ·
All issues in lapce/lapce.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug quarto-hub
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
quarto-dev/q2#721 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
frontend maui-pilot pilot-ask question
Difficulty 2/5 1-3 hours Newbie friendliness 75/100