Post

📚Are you watching closely? #AshFramework #ElixirLang

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.

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.

Since Phoenix generators create test files automatically, you might want to consider adding something similar to help developers get started.

Agreed, I'd like to add a test generator. The phoenix generators make a lot of assumptions and ultimately set you up with something far less powerful/flexible than an Ash.Resource. Application logic being a bag of functions is something that IMO helps when you start but that you pay 👇🏻

a significant cost for down the line. We're trying to be the middle ground. Sacrificing power and flexibility for the sake of the on ramp isn't an option. It will always be harder to learn Ash than to learn the patterns in Phoenix contexts, but its also that much more useful if you can break 👇🏻