This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-27
Channels
- # beginners (35)
- # boot (111)
- # cider (12)
- # clojure (295)
- # clojure-android (2)
- # clojure-dev (12)
- # clojure-dusseldorf (9)
- # clojure-finland (1)
- # clojure-greece (7)
- # clojure-italy (24)
- # clojure-norway (1)
- # clojure-poland (7)
- # clojure-russia (14)
- # clojure-sg (1)
- # clojure-spec (29)
- # clojure-uk (25)
- # clojurebridge (1)
- # clojurescript (157)
- # clr (3)
- # cursive (3)
- # datomic (55)
- # docker (6)
- # hoplon (4)
- # juxt (11)
- # leiningen (13)
- # luminus (1)
- # lumo (3)
- # mount (1)
- # off-topic (47)
- # om (43)
- # onyx (35)
- # re-frame (33)
- # reactive (2)
- # reagent (4)
- # rum (3)
- # schema (5)
- # specter (5)
- # test-check (63)
- # vim (15)
- # yada (14)
Is it possible to protect the swagger API made by yada/swaggered
using the same auth as yada resources?
Yes. But use the 'simple' rather than 'easy' way
See the docs. Afk sorry!
14.1.3
I'm sure there's a direct link ;)
If you get stuck let me know. Summer of yada starts next week!
(For regular listeners, the 'summer of yada' starts when I move house on May 4th and return to a regular routine of yada development)
Begun the yada development has.
I have a similar question about classpath-resource and webjar-resource. Normally I can protect a resource by composing it (it’s just a map to which I can add stuff and call yada/resource
on to validate). This doesn’t seem to work here. Maybe it has to do with how sub-resources work. Something for tomorrow I guess.