purescript / purescript/pursuit
Adding the possibility for CORS requests to the pursuit API
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
I'm building a webapp where I'd like to add pursuit search, but fetch requests to pursuit are failing due to access control issues.
I think this could be solved by adding ie:
optionsSearchR :: Handler RepPlain
optionsSearchR = do
addHeader "Access-Control-Allow-Origin" "*"
addHeader "Access-Control-Allow-Methods" "GET, OPTIONS"
return $ RepPlain $ toContent ("" :: Text)
getSearchR :: Handler TypedContent
getSearchR = do
addHeader "Access-Control-Allow-Origin" "*"
Are there any objections to this? If not I'll make a PR.
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
Locate the pursuit API handlers for the search endpoint, especially optionsSearchR and getSearchR mentioned in the issue. Check how request methods and response headers are handled there, then verify that browser search requests and their OPTIONS preflight receive the requested CORS headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100