This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-23
Channels
- # babashka (104)
- # beginners (23)
- # calva (15)
- # cider (2)
- # clojure (29)
- # clojure-europe (14)
- # clojure-nl (2)
- # clojure-norway (3)
- # clojure-spec (4)
- # clojure-switzerland (1)
- # cursive (3)
- # datomic (6)
- # emacs (17)
- # etaoin (2)
- # expound (1)
- # fulcro (4)
- # graphql (4)
- # honeysql (7)
- # introduce-yourself (2)
- # jackdaw (5)
- # malli (3)
- # meander (19)
- # nbb (3)
- # off-topic (35)
- # pathom (6)
- # pedestal (4)
- # polylith (31)
- # rdf (11)
- # re-frame (8)
- # reitit (6)
- # shadow-cljs (8)
- # specter (4)
- # squint (15)
- # vim (6)
Hey folks, anyone know about support for INPUT_FIELD_DEFINITION | ARGUMENT_DEFINITION directives in Lacinia. The docs mention it's changing fast so just wondering if there's something in the pipeline currently and if it has an ETA. Or alternatively if there's something I could work on, I can try my hand at some changes but it would be useful if there's a plan in mind for the implementation as it's probably reasonably far reaching.
I've come across the apply-field-directives stuff so could follow that pattern perhaps (haven't looked far into the source yet)
FWIW I started looking into the code, it seems like Directives are extracted and compiled in the source but only field-directives are really support for swapping in logic from one place. I've started messing around with some code that follows a similar pattern in order to interpret other directives but it might end up being only useful to me if the planned route is significantly different.
WIP getting somewhere https://github.com/GreshamDanielStephens/lacinia/pull/1/files?diff=split&w=1 Note Haven't managed to work out the formatting yet so above link hides whitespace, clearly I have some different settings and couldn't see a deps job to run a formatter if anyone knows how. I don't want to change my settings since I have them for work.