practicalli / practicalli/clojure-web-services
reitit routing coercion and testing
Open
Nobody has claimed this yet.
reitit
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
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 reading the linked article on automatically generated API tests with Clojure and reitit, then inspect the repository for existing reitit routing, coercion, and test entry points. The issue does not identify files, current behavior, or acceptance criteria, so the expected completed behavior needs clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend-api-design, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100