This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-02
Channels
- # announcements (1)
- # beginners (15)
- # calva (6)
- # cider (72)
- # clojure (105)
- # clojure-europe (2)
- # clojure-france (1)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-uk (32)
- # clojurescript (14)
- # code-reviews (10)
- # cursive (8)
- # data-science (2)
- # datomic (38)
- # events (1)
- # fulcro (31)
- # graphql (1)
- # hyperfiddle (47)
- # java (4)
- # jobs (4)
- # off-topic (18)
- # overtone (2)
- # parinfer (12)
- # pathom (19)
- # pedestal (4)
- # philosophy (2)
- # portkey (22)
- # re-frame (42)
- # reagent (1)
- # rum (1)
- # shadow-cljs (36)
- # specter (3)
- # tools-deps (2)
good morning and happy new year clojurians, I was hoping it would be ok to ask you a question. I’m looking to implement a jasonapi complient microservice using pedestal but I’m faced with a challenge, I am not sure pedestal supports filtering and pagination in the way that the jsonapi standard defines it (i.e. filter[name]&page[3] - https://jsonapi.org/format/#fetching-pagination). Is this feature to parse multimap queryparams available in pedestal?. Thank you #pedestal
@ariel.silverman AFAIK, those parameters will result in a params map of {:filter[name] nil :page[3] nil}
.
Thank you, I was hoping to get some clarity about how to parse parameters of this sort, for example say for an input of filter[name]=somename&filter[id]=123 getting a nested map that looks like {:filter {:name "somename" :id 123} }
@ariel.silverman, as of now you’d need to create an interceptor to do that transformation for you
Thank you, I was hoping to get some clarity about how to parse parameters of this sort, for example say for an input of filter[name]=somename&filter[id]=123 getting a nested map that looks like {:filter {:name "somename" :id 123} }