This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-15
Channels
- # babashka (4)
- # beginners (136)
- # calva (63)
- # clerk (7)
- # clj-kondo (8)
- # clojure (43)
- # clojure-boston (1)
- # clojure-europe (37)
- # clojure-nl (1)
- # clojure-norway (11)
- # clojure-uk (3)
- # clojurescript (6)
- # clr (1)
- # code-reviews (16)
- # cursive (45)
- # datomic (2)
- # docker (32)
- # emacs (10)
- # events (2)
- # exercism (1)
- # fulcro (3)
- # hugsql (1)
- # hyperfiddle (47)
- # leiningen (3)
- # lsp (30)
- # malli (39)
- # missionary (1)
- # off-topic (24)
- # pathom (2)
- # portal (14)
- # practicalli (5)
- # rdf (13)
- # reagent (18)
- # reitit (18)
- # releases (7)
- # remote-jobs (1)
- # sci (2)
- # shadow-cljs (45)
- # sql (7)
- # tools-build (11)
- # xtdb (13)
if others are interested in reitit openapi3 support, feel free to try out the latest git master of reitit! leave your comments here: https://github.com/metosin/reitit/issues/84
thanks for your comments @U06HHF230
You’re welcome, and thanks again for the PR! It’s a great contribution 🙇
What git coordinates would I use to get the latest reitit from git using a deps.edn file? I tried specifying :git/repo
and :deps/root
but it doesn't resolve properly.
The latest release is still 0.6.0
which doesn’t include the openapi3 stuff. If that’s the stuff you’re wanting to use then I think you need to checkout the latest from master
and build/install it locally yourself with a version of something like 0.7.0-SNAPSHOT
IIRC I did something like this (apologies but I’ve not checked these commands; just from memory):
1) checkout the master branch
2) run ./scripts/set-version 0.7.0-SNAPSHOT
3) run ./scripts/lein-modules install
Then I updated my projects deps.edn to use 0.7.0-SNAPSHOT
.
for lein-to-lein, https://github.com/technomancy/leiningen/blob/master/doc/TUTORIAL.md#checkout-dependencies
Hi @US1LTFF6D, is there an estimated release date for Reitit openapi 3 support? I've been using the master branch the last few days and it has been working great
Pretty much all the pieces are in place, we just need to do some release engineering before we can get the next reitit release out
Oh great thank you and thanks for all the awesome work you are doing
I’d like to define a catch all route in a dynamic routing subtree. I can set {:conflict nil}
but then I need to ensure that the catch-all is always evaluated last. Obviously I can do something like (concat (generate-dynamic-routes) [catch-all])
but I’m wondering if there’s another way, e.g. to explicitly specify a :fallback
in the options or something like that?
There is also :conflicting true
route data you can set for the conflicting routes, but just ignores those routes from the conflicting list.
ok cool thanks for clarifying 🙇