Add support for Http.riskyRequest, Http.riskyTask
Open
enhancement
- Dominant language
- Elm
- Stars
- 95
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
What is different between risky and non-risky requests that someone would want to assert about?
Contributor guide
Research direction
Start by reading the existing Http.riskyRequest and Http.riskyTask entry points and their related tests, then compare them with the non-risky request and task APIs. Determine which observable differences users need to assert and document the expected behavior before implementing support and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elm
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100