metosin / metosin/compojure-api
Compojure 2.x should be backwards compatible with 1.x
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1.1k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
- add back
:formatoptions to use ring-middleware-format- consider pulling out muuntaja api-middleware into another function
- Q: if neither
:formatnor:formatsis provided, which do coercion backend do we choose?- either need to break 1.x or 2.0.0-alphas
- could make even more explicit with a keyword option explicitly naming backend
- still, which to default to?
- also need a way to set the default for namespaces we don't control via JVM properties
- coercion defaults have changed with muuntaja. if we silently upgrade 1.x users to muuntaja, we should keep 1.x defaults.
- Q: if neither
- consider pulling out muuntaja api-middleware into another function
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
The issue concerns restoring :format options, deciding how coercion defaults interact with Muuntaja, and preserving Compojure 1.x behavior. No files, tests, or entry points are named; first map these options and defaults in the repository, then verify that legacy configurations and namespace-level defaults remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100