I second that. Spark docs would be great.
CharlesIrvine
zachdaniel
Creator of Ash
Spark is its own project in its own right, unrelated to Ash. In fact I think if it gets some half-decent documentation, I’d expect it to be more popular than Ash 
.The only problem is one of time on my end. It is fully supported (separate from its usage in Ash) and there are other non-ash projects using it. They just had to brave its lack of docs. But it is stable and feature-full. Documenting it has always been one of those “as soon as I have some time” projects and, lo and behold the day never comes.
4
D4no0
This is great to hear.
I don’t think the documentation needs a lot of effort, a few examples of different possibilities in readme would be more than enough to get me going, as everything else related to available macros/functions is pretty well documented.
1
zachdaniel
Creator of Ash
True, it’s likely an 80/20 thing, can get 80% of the value without much effort. I’ll put something on my list, will probably be next week or the week after at the earliest I can get to it.
1
sodapopcan
True dat. I feel this way about man pages—the only reason people think they suck is because they lack examples (I understand it’s a storage concern but still).
0
zachdaniel
Creator of Ash
Well, we have about 35 in the form of every DSL & extension written for Ash And the test suite defines some more 
EDIT: here is a small one, for example: ash_archival/lib/ash_archival/resource/resource.ex at main · ash-project/ash_archival · GitHub
2
BartOtten
No it did not generate DSL, but functions for schema’s. So MyStuct would cause a list_my_structs/1 with field filters.
Ash does a lot more than what my macro’s did and in a composable way. Oh, and Ash has a lot more documentation!
0
DaAnalyst
