Question: maybe I will start there. Is there a low-friction way to convert specs to schema or does one still have to hand-ball the schema afterwards? Thanks

Asked By
Asked At
2018-01-16 15:21:58

Found 15 possible answers.

User Answered At Possible Answer
conan 2018-01-16 15:22:35 i'd just get the hang of sticking some specs together for whatever data you already have. the fact that they're all namespaced keywords is very convenient when it comes to making datomic schema from them i did it all by hand
maleghast 2018-01-16 15:22:50 OK :slightly_smiling_face: Cool
conan 2018-01-16 15:23:00 it's simple, if not easy :smile:
maleghast 2018-01-16 15:23:05 hehe If it were easy EVERYONE would be doing it…
shan 2018-01-16 15:23:27 RE: specs Spotted this on
conan 2018-01-16 15:26:16 oh handy
maleghast 2018-01-16 15:30:19 Yeah, that’s a handy resource for sure - thanks @shan
yogidevbear 2018-01-16 15:30:22 Yeah @shan , I saw someone tweeting about that the other day too
maleghast 2018-01-16 15:35:40 Have people reached a consensus yet about how to organise / store and use specs..? I realise that the beauty of this is that as long as I can access them and don’t break anything else that I can do it any way I damn well please, but I am generally interested in at least knowing about the “best practice” way of doing something, even if that may change or is the subject of some debate… I mean do they “live” in .edn files in say “/resources/specs” and then as part of the app initialisation we read them in, or do they co-exist in namespaces that need them, or something else entirely..?
conan 2018-01-16 15:40:02 i put mine in a namespace that's modelling the thing they're for. so for example, i have a person namespace, and it contains all the specs that are :person/full-name and stuff try to keep it together so you always have the specs you need near to hand. i think this makes sense when you have an fdef next to each of your functions too
maleghast 2018-01-16 15:40:55 fdef?
thomas 2018-01-16 15:43:21 a spec for functions if I am not mistaken
maleghast 2018-01-16 15:43:28 Oh right… realises that there is more reading to be done…
thomas 2018-01-16 15:46:57 and the curated list of specs is a cool and very good idea!
maleghast 2018-01-16 16:03:12 @conan - Would you be prepared to share / show your person namespace - a lot of the documentation I am trying to use to get my head around all of this is very fragmented when all I __really__ want / need is a complete example… (totally understand if not - I realise it might be proprietary etc - but I thought I may as well ask :wink: )

Related Questions