Post

Every time I try to start with ash, I get stuck. I tried with tdd which is very easy in phoenix or rails because the error often guides you what to do next. With ash it's not that obvious.

I think that you should record someone with elixir knowledge but without ash experience trying to copy something in ash and see where they struggle. Similary what Primeagen did when learning elixir.

Have the ash docs linked to examples of that feature in a real world example repo. Same with Phoenix and LiveBeats. Force LiveBeats repo to stay up to date because the docs reference it. Great for example based learners like myself. Wanna see custom policies in action? Click here.

You should share where you get stuck :) We have a lot of people in the community willing to help, all you have to do is ask. Let us know where you got stuck in a GitHub issue or on ElixirForum/discord 🙇‍♂️

I appreciate the community's help, but when I get stuck on basic concepts, I know I'll struggle even more with advanced topics. One major blocker was the lack of test examples. While there is a page in the documentation about testing, it doesn't cover important areas like relationships.

My usual approach is to start with a test and let the compiler errors guide me. However, in this case, the errors were so cryptic that I had to abandon the effort. The ash_hq and realworld examples have very few tests, which doesn't help.