ash

@jaynus

From Discord conversation regarding alternative destinations (image, video, memory buffer) for rendy graphs, we need an example of rendering screenshots through rendy.

Is your feature request related to a problem? Please describe.
Many to many relationships are a little verbose. Also, the current default for destination_field_on_join_table would use the relationship name (tags_id), instead of the resource name (tag_id)

Describe the solution you'd like
The source and destination join table fields in many to many relationships can be derived with th

There was something in place for short period, but it was insufficient and was removed. We should support writing to and reading from join table via the meta field on the relevant resource identifiers.

Proposal: Add a tenant_schema/1 callback to AshPostgres.Repo which takes any input from a tenant: param and returns a schema string.

Is your feature request related to a problem? Please describe.
Given the type attribute(:roles, {:array, :atom}, it is possible but clunky to use has and boolean logic with and to filter on where the roles field contains all items in a given list.

Describe the solution you'd like
I would like a filter function akin to roles has all items in [opts] that would handle that logi