v0.5.0

Breaking Changes

• Relationship and typeahead options for a multitenant related resource without an authorizer now use the tenant assign the way Ash.read/2 does. With attribute multitenancy only that tenant's records are listed, and without a tenant assign the field raises a tenant-required error unless the resource or its read action allows global reads. Before, these options ignored the tenant and listed every tenant's records, or read the default schema with context multitenancy. Related resources with an authorizer already behaved this way. See Upgrading to 0.5.

Bug Fixes

• Relationship and typeahead options no longer read the whole related table. When the related resource had an authorizer, every record the actor could read was loaded to restrict the options by id, which timed out forms on large tables. Policies that resolve to filters are now applied to the options query; only policies that need runtime checks still read the authorized records. (#39)

Full Changelog: v0.4.1...v0.5.0