Ahh, that doc is out of date for 3.0, sorry! Using exception modules like that is “the way”, the only difference is that all our errors are exceptions, so you’d use .exception as if it was any other error. It’s all powered by the library (which was extracted out of Ash) called Splode API Reference — splode v0.3.1
Then, these errors have a specific protocol defined for them to allow them to be exposed over an API (differs depending on the API). You can also define your own errors and use those, if you implement the appropriate protocol.
You can see examples here: ash_graphql/lib/error.ex at main · ash-project/ash_graphql · GitHub
