ash

@jaynus

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

Due to the filter-based implementation of keyset pagination, it cannot be used with sorts on calculations.

We could solve this problem by making the keyset only be the primary key of the record, and then fetching that value loading the calculations/aggregates that we need. If we do this we should either: 1.) make it a new pagination mode or 2.) add an option like mode: :strict | :fetch (name

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

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.

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