ash

@jaynus

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

Too many extensions currently break if you add anything other than alphanumeric and underscores to an attribute/calculation/aggregate/relationship name. For now, we should simply prevent this at the resource level.

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

Currently, the sort_input only considers attributes and arguments (it was written before calculation sortability was created).

https://github.com/ash-project/ash_graphql/blob/master/lib/resource/resource.ex#L2005

What we likely need to do is have an option when using use AshGraphql like sort_schema: :simple | :complex, with :simple being the default. Eventually we may actually just re

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.