max-mapper / max-mapper/nugget
errror on 300 or higher,
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 178
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
the only time you'd care about a 300-399 would be a 304 right? (maybe a 300 but I don't see that one very often), upon first read it sounded like I had to do manual redirects.
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
Start by reproducing the reported behavior for HTTP 300–399 responses in nugget, then inspect the relevant response-handling entry point. Clarify whether statuses such as 300 and 304 should be treated differently from redirects, and document or test the intended behavior before making a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100