This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-11
Channels
- # babashka (13)
- # beginners (17)
- # bristol-clojurians (1)
- # calva (23)
- # cider (5)
- # clj-kondo (32)
- # cljsrn (2)
- # clojure (167)
- # clojure-dev (23)
- # clojure-europe (6)
- # clojure-uk (8)
- # clojurescript (5)
- # cursive (7)
- # datomic (12)
- # emacs (4)
- # events (6)
- # fulcro (2)
- # graalvm (1)
- # interop (10)
- # leiningen (8)
- # local-first-clojure (1)
- # luminus (2)
- # meander (36)
- # planck (3)
- # re-frame (3)
- # reagent (3)
- # sci (2)
- # spacemacs (4)
- # sql (1)
- # test-check (6)
- # tools-deps (22)
- # xtdb (75)
Hi!
I'm following the book: Web Development with Clojure and doing the examples alongside with the book. There's a chapter where the schema validation logic is moved from the clj
to cljc
so that it can be shared with the front end validation as well.
The problem that I'm having is that: Even if the code compiles and runs without errors, the validation logic seems not to be triggered, neither at front end form or the back end endpoint.
I'm not sure if I'm missing a step here or just doing something plain wrong. Any tips would be appreciated! Thanks!
hey team noob q -- what do folks use for web servers? I used jetty, but I wonder if there are better alternatives that are more idiomatic to clojure -- I saw immutant -- looks interesting, but am not sure if it is actively maintined, etc
I use http-kit. Fortunately, any ring compatible server feels fairly idiomatic to me
We use the embedded Jetty server in production.
We used http-kit in production for a while but, while it was fast and reliable, New Relic's agent isn't compatible with it and we wanted better telemetry, so we switched to Jetty.
We were originally using an earlier version of Jetty and it was a bit buggy -- we kept seeing random thread death errors in production, which was why we switched to http-kit for a while.
@dimitar.ouzounoff Just for Clojure? I wouldn't bother learning OO patterns, except as a way to understand more of the benefits of FP in several of those cases...
Many OO patterns (for Java etc) come down to "just functions" in an FP context. There are FP patterns as well/instead tho'...
This is a good talk on that @dimitar.ouzounoff https://www.infoq.com/presentations/Clojure-Design-Patterns/
This is a nice, tongue-in-cheek romp through common OO patterns and what they would look like in FP http://mishadoff.com/blog/clojure-design-patterns/
(but, be aware, it's a bit of a simplification and deliberately a bit provocative 🙂 )
thanks! I will watch this presentation now.
watching Stuart Sierra’s presentation I reached to conclusion that I need to learn more about architectural patterns, not design patterns