This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-24
Channels
- # beginners (15)
- # boot (4)
- # cider (1)
- # cljs-dev (2)
- # cljsrn (5)
- # clojure (124)
- # clojure-france (2)
- # clojure-russia (22)
- # clojure-uk (10)
- # clojurescript (50)
- # core-async (5)
- # cursive (3)
- # datomic (8)
- # emacs (2)
- # fulcro (10)
- # hoplon (8)
- # jobs (4)
- # luminus (2)
- # lumo (7)
- # off-topic (14)
- # portkey (7)
- # re-frame (22)
- # reagent (2)
- # shadow-cljs (3)
- # spacemacs (1)
- # yada (26)
greetings ! I'm looking to "Get Started" with yada-lean, but the User Guide points me to juxt/edge - which is way too packed with stuff for my sunday evening endeavor
Phonebook
That's the crud thing worth understanding
the fact that I'm a lein guy that doesn't know much about boot yet adds to the time it takes me to get a simple yada-lean webserver up and running 🙂 not to mention the component scaffold I'm also getting aquainted with
Extensions. Yada has a small core and the functionality is built out with extensions.
from my perspective, no way to understand Yada or Yada exemples without understanding stuartsierra/component
first
Regarding Basics, Introduction part of the manual it says "It achieves this by providing you with a highly-configurable handler that is general enough to use in the vast majority of cases. Rather than coding the handler, the developer only has to configure one. This declarative approach provides greater scope for accuracy, consistency and re-use."
am I correct in my understanding that this declarative approach is powered by stuartsierra/component
?
after cloning the yada repo, and starting the dev system using (dev)
then (go)
, hitting
will only serve 404 not founds whereas
will serve the manual
@zor you can treat yadas server just the same way you would a jetty one, so defing it will work fine
You just some nice properties from component, but it's not essential to Yadaitself
Nope, this is by declaring a yada/resource
and filling in the blanks about which methods the resource supports, how to fetch properties, e.t.c. From that small description, yada can generate rich behaviour that matches the HTTP spec, including authorization, authentication, caching, good error messages, validation, e.t.c.
that's the meat of it yes, what the manual talks about in good details - I've mostly skimmed so far
@danielcompton how do I serve this yada resource or otherwise play with it from the REPL ?