@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.

Right now, we don't validate that filters/sorts only use the fields exposed in the json api, which would be a big problem if someone used this in production (if anyone is reading this issue, and ash is still in alpha, and you used it in production and somehow exposed some data about your system, it is your fault :) )

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.