This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-27
Channels
- # announcements (4)
- # asami (6)
- # aws-lambda (1)
- # babashka (38)
- # babashka-sci-dev (20)
- # beginners (87)
- # calva (67)
- # cider (19)
- # clerk (13)
- # clojure (102)
- # clojure-europe (52)
- # clojure-filipino (1)
- # clojure-hungary (4)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-sweden (3)
- # clojure-uk (1)
- # cursive (13)
- # data-science (7)
- # datomic (8)
- # deps-new (1)
- # emacs (3)
- # fulcro (16)
- # graphql (3)
- # humbleui (3)
- # kaocha (3)
- # leiningen (3)
- # malli (3)
- # off-topic (14)
- # pathom (34)
- # polylith (4)
- # rdf (12)
- # reitit (3)
- # releases (1)
- # remote-jobs (7)
- # rum (2)
- # sci (22)
- # shadow-cljs (115)
- # tools-deps (26)
- # tree-sitter (29)
["/tipo-treinamento"
{:get
{:handler
#function[ti.routes.api.tipo-treinamento/get-tipo-treinamento],
:responses
{200
{:body
[:vector
..elided
]}}},
:post
{:handler
#function[ti.routes.api.tipo-treinamento/post-tipo-treinamento],
:parameters
{:body
..elided
}}}
["/:id"
{:post
{:handler
#function[ti.routes.api.tipo-treinamento/update-tipo-treinamento]}}]]
Is that a valid nested router. It's inside ["/api" here ]it generates a get on /tipo-treinamento/:id which I dont want.
if I flatten it works. I'm asking here to see if it's a issue or to be taught 🙂