This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-11
Channels
- # aws (6)
- # beginners (167)
- # cider (41)
- # cljs-dev (6)
- # cljsrn (3)
- # clojure (399)
- # clojure-dusseldorf (1)
- # clojure-nl (2)
- # clojure-spec (3)
- # clojure-uk (47)
- # clojurescript (16)
- # core-async (8)
- # cursive (56)
- # datomic (14)
- # devcards (1)
- # docs (2)
- # duct (2)
- # editors (3)
- # emacs (3)
- # fulcro (178)
- # graphql (10)
- # off-topic (107)
- # onyx (7)
- # pedestal (21)
- # planck (13)
- # re-frame (58)
- # reagent (76)
- # ring-swagger (3)
- # shadow-cljs (85)
- # slack-help (2)
- # sql (1)
- # tools-deps (11)
- # uncomplicate (5)
- # vim (24)
- # yada (4)
@hlship Mainly just that Paul (the primary steward until now) has to devote his time to personal life for the foreseeable. I'm the maintainer at the moment with a pretty full plate.
I'd love to hear from @channel what they need from Pedestal. IMO, the foundation is strong so I don't see a lot of pending work in the core. So post your wishlist and we can start to build a roadmap together.
Did you notice this PR? https://github.com/pedestal/pedestal/pull/551
@mtnygard one of the things I’d like to help with is fleshing out the guides more. It can be frustrating when learning pedestal to click on a guide link only to see a placeholder template. I’ve thought about contributing some but notice that PRs seem to stagnate, so haven’t put in the time yet.
Great! I’ll see where I can help and will work on some PRs over the next few weeks. Would you be open to a PR that removes any link to a guide that does not yet exist (to remove the tease) for the time being?
Well, I did put in the placeholders to encourage contributions, not just to tease people.
But if your experience is that they're discouraging, then go ahead and send that PR.
I would like to see the interceptor model extracted into a specification, like Ring: no pedestal-based keys, pluggable async and support for ClojureScript.
@ikitommi Are you more interested in using interceptors in front-end apps or in back-end CLJS? Just curious.
both. re-frame has interceptors, but bit different, (`:before` and :after
and with bit different semantics) and would be great for Clojure/Script story to be able to run ~same web apps on both server targets.
I found that, when implementing GraphQL subscriptions for Lacinia, using Pedestal web sockets, there existing API was quite opinionated and I had to do a kind of "end run" around the preconceptions: https://github.com/walmartlabs/lacinia-pedestal/blob/5fa4c02be0c9fb97ebfb288e3dd5eda12d09f07e/src/com/walmartlabs/lacinia/pedestal.clj#L608
It feels like there's a simpler API buried in there, and the current API should be a convenience layer on top of that.