practicalli / practicalli/clojure-web-services

reitit: overview and extensive guides - creating an API from scratch

Open
#132 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API reitit
Dominant language
Markdown
Stars
16
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Create a simple to follow set of guides to using Reitit and Reitit-ring (for web services), based on experiences of Reitit use over several commercial projects.

  • Overview of reitit
  • Creating web routes (REPL driven development)
  • Building an API step by step with Reitit & Reitit-ring
    • Defining a router
    • Default routes
    • Muutanna middleware
    • Custom middleware
    • 404 error management (useful feedback)
    • Creating an api
    • Adding Specifications to the API
    • Authentication & Authorisation for the API
    • Adding versioning to an API
    • Open API (Swagger UI) & API testing
      • adding an API key in the Swagger UI for testing
      • customising the Swagger UI / Company branding and standards
    • Designing Interceptors (how and why)

NOTE: examples of these aspects are already included in Practicalli Project Templates however this updated guide will help people understand the code in detail and the design choices made.

Related issues: #13#131

resources

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing Practicalli Project Templates and the linked Reitit, Reitit-ring, and default-handler resources. Plan the guide around the listed topics, from routing through authentication, versioning, OpenAPI, and interceptors. Done means a simple, coherent set of step-by-step guides covering the requested API-building journey.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
api, backend, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.