macchiato-framework / macchiato-framework/macchiato-core

Input & output validation with api-docs (swagger)

Open
#7 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Clojure
Stars
385
Forks
33
PR merge metrics
No merged PRs in 30d

Description

Optional & pluggable, for handlers, maybe also for middleware. Schema is awesome and proven per today, Spec is the probable future. I could pull out a proposal for a common structure for input & output coercion with api-docs, based on our libs.

  • simple, data-driven core
  • optionally "easy" macro sugar with inferred models
  • pluggable implementation (schema, spec, other)
  • protocols for routing libs to collect routes for api-docs
  • swagger-docs (ring/spec-swagger)

what do you think?

Contributor guide

No contributing guide indexed for this repository

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

The issue names no files, tests, or entry points; start by reviewing the proposal and the referenced Metosin libraries. Agree on the common structure, supported schema/spec implementations, routing integration, and Swagger output before implementation, since the issue does not define what done looks like.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.