purescript / purescript/pursuit
Parentheses break searches for operators
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
For example, @thimoteus pointed out in Slack that a search for <$> works fine, but a search for (<$>) gives none of the desired results.
They should probably yield the same results. (@hdgarrood asked that this be reported.)
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.
Research direction
Reproduce the two linked Pursuit searches, comparing the operator query with and without parentheses. Trace the search handling for operator expressions and determine what needs to change so both forms return the same results; done means the parenthesized search matches the unparenthesized one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100