ash

@jaynus

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

When creating a new Ash.Type i.e: to support Range column types in Postgresql, it is common practice to install a type for Ecto and then to stub the Ash.Type callbacks with calls to the Ecto type, this works for the most part, except for when referring to a custom type from within a calculation.

Ash seems to use the value returned by the type callback verbatim, however when you pass in a module

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

I've laid the groundwork for relay support, pushed to master now. There are three remaining steps:

• when fetching :has_many or :many_to_many relationships, we need to wrap them in a connection if the destination action supports pagination
• when selecting fields, we need to look at the selections inside of the ["edges", "node"] path
• we need to build the actual connection object. I've

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.