Zach Daniel

Being able to do this would turn this tool from a great tool to a quintessential tool for me :)

If a related resource is not being included in the schema because its api is not in the schema, then we should raise an error at compile time with instructions...

Yeah, that is a great idea :)

We would make operations work on top of old snapshots, so it wouldn't be a breaking change (i.e require removing/doing surgery on snapshots), and I think there may actually be...

We actually want to make these operations part of core, so that any extension can react to these changes.

🤔 yeah, this is interesting. There is a way to add custom unique indexes to be checked in the changeset. Specifically: ```elixir postgres do unique_index_names {[:provider, :provider_id], "...name of constraint"}...

Anyone who wants to champion this is more than welcome! There are all kinds of things that could be added to the schema at the moment. We may, however, want...

We won't be able to accept any arbitrary value, as currently the tenant is expected to be a string everywhere in the framework. What we could potentially do is have...

need to run `mix ash.formatter`, additionally, we should change the `default_resource_action` in the api page to be `:read` instead of `:primary_read`, likely :)

Otherwise looks great!