Looking for opinions on this idea: https://github.com/walmartlabs/lacinia/issues/188

honestly this feels like something for a sort of sidecar feature

it’s not that hard to decorate edn data

or compose it really

hell, in our app I have a bunch of helper functions for describing our schema

since the schema is fairly sprawling

and this lets me compose it more readily

so I can do things like:

that might not be the best example, but everything else I have is too domain-specific

but I’ve found it’s much easier to sling data around with code

anyway if you parsed the markdown file into sections so you had {:User "An external user." :User/family-name "..."} and so forth it would be fairly easy I think to walk the schema edn and decorate it with data from that

That's kind of the intent.

This could be something as an add-on library.

But so could attach-resolvers. It's kind of fundamental, and supporting excellent documentation is a goal. My thinking is that embedding the documentation in the EDN does not support that goal.

that’s fair

https://twitter.com/oliyh/status/996085445892165632?s=09