ash

@jaynus

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

First thing I tried to do for read actions was implement fetch all and fetch by id, and ended up with this:

  actions
    read :all do
      primary? true
    end

    read :get_by_id
  end

  code_interface do
    define_for Api

    define :all, action: :all
    define :get_by_id, action: :get_by_id, args: [:id], get?: true
  end

I assumed that the `define :get

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.