practicalli / practicalli/clojure-web-services
API design principles
Open
Nobody has claimed this yet.
API
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
https://news.ycombinator.com/item?id=24383180
Video: How To Design A Good API and Why it Matters
https://youtu.be/heh4OeB9A-c
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
Review the linked Hacker News discussion and video first; the issue names no file, test, or concrete change. Clarify whether a documentation update is wanted, then identify its target location and define what completion should mean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- api, backend-api-design
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100