Found 11 possible answers.
|User||Answered At||Possible Answer|
(ns experiments.a creates infinite recursion?
[:test (not (isa? (type ?o) ExcludedType))]) [?o <- Object] You could probably do what you ask though:
- Is there a version of this for cljs?
- so, you are write a new version in JS?
- Is there a way to have a cljs repl like lumo or planck run a version of cljs that you just built? I suppose I can just clone lumo and build it with the new version. lol
- does anyone know if its possible to add new schema to a running db?
- the form what took in schema?
- I think I got the answer(s) I was looking for, but I’ll add a bit of context here in case you have further advice: I am generating a GraphQL schema from an application schema (database schema + some extra info). I am doing this as a sequence of transformations on a “schema” map. So I start with an empty map, then generate some object types, then generate some queries, etc @noisesmith how is it inside the call to g? the result of h is passed as an argument I’ll stop there to avoid spamming this channel with unecessary details ``` (keys (:nodes hodl-config))))) (map #(gen-for-node hodl-config config %) So I have code similar to this```(apply comp The reason I was expecting to reach high number of compositions (in the low hundreds) was because some of my transformation steps should be executed for each entity type and I am composing those I wrote each transformation as a function that takes two config maps and extra options, and return a 1-arity function which takes a schema and returns a schema
- @vinnyataide: Do you mean Datomic schema handling? If so Fulcro uses something forked from Yuppiechef's schema.
- @drewverlee what you mean by db schema on this context?
- @sekao Haven’t tried that version. I’m on 1.9.854 What version of Clara are you using? I’ve had problems with the schema library in the past though. I think I got around it by excluding clara’s version and using a newer one. That might not work in this case though
- I use Figwheel to run cljs, and it looks like that CIDER is in a known broken state when it comes to cljs repls. I am wondering, is there a work around for this issue or should I revert to a previous version of CIDER?