@jaynus

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

In order to support tracing and metrics, we'll want to emit start/stop events around all major framework operations.

This json object: https://github.com/ash-project/ash_json_api/blob/master/lib/ash_json_api/json_schema/json_schema.ex#L556 should have a required key (like attributes), which should be any relationship marked as required (only belongs_to relationships can be required at the moment). This only needs to be on post. For updates, the relationship will have already been set.

Right now, we create a snapshot for each resource. In order to create (and rollback) extensions in the migration generator, we will need to track another snapshot just for the repo, and we would currently only store the list of extensions. Then, when migrations are generated, we'd go through each resource in each API, grab their repo, unique them, and create snapshot for them w/ their extensions.