Ash 3.0 Teasers!

[rbino]

@zachdaniel

domain option to use Ash.Resource

When creating a resource, you pass the domain option. For example:

defmodule MyApp.Accounts.User do
  use Ash.Resource,
    domain: MyApp.Accounts
end

This static configuration can be used in various places where you would have previously had to specify an api. For example, you no longer need to specify define_for in the code_interface block.

I have a doubt about this: I’m trying this out in Ash 2.20.3 (using api instead), and indeed it works when removing define_for, but another place I’d expect this to work is to avoid defining the api option for cross-domain/api relationships, but if I remove the api option Ash complains about it being missing.

Is this intended, a bug or an Ash 2.x limitation?