practicalli / practicalli/clojure-web-services
Reitit projects testing and authorisation references
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Projects
https://github.com/prestancedesign/usermanager-reitit-example
https://github.com/prestancedesign/todo-backend-reitit
https://github.com/dawranliou/comment - reitit, integrant, hugsql
Testing
https://dev.solita.fi/2021/03/05/automatically-generated-api-tests-with-clojure-and-reitit.html
Authorisation with reitit
https://medium.com/@maison.moa/using-jwt-json-web-tokens-to-authorize-users-and-protect-api-routes-3e04a1453c3e
https://github.com/ovotech/ring-jwt
https://jwt.io/introduction
https://github.com/schaueho/reitit-with-ring-jwt-poc
https://cljdoc.org/d/tolitius/funcade/0.1.17/api/funcade.middleware.reitit
https://stackoverflow.com/questions/33265812/best-http-authorization-header-type-for-jwt
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization
https://github.com/metosin/reitit/issues/185
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 reviewing the linked Reitit project examples and the references on testing, JWT authorization, Ring middleware, and Swagger. The issue does not name a file, entry point, or specific documentation change, so the intended scope and completion criteria need to be established before work can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100