You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple ways to query artworks on gravity, so we want to be able to handle them transparently behind the scenes depending on the fields in the query.
Not sure if this is what you mean by the tricky bit, but one issue I see is with the additional 'hits' field that hosts the artworks vs without the filter.
@orta@mzikherman Been thinking about the above mentioned issue a bit more, what about if we switch to the Relay ‘Connections’ specification for associations? It adds a bit more ceremony, but it does allow arbitrary metadata on any association, such as e.g. a count. This would for the unfiltered and filtered artworks to both follow the same shapes.
There are multiple ways to query artworks on gravity, so we want to be able to handle them transparently behind the scenes depending on the fields in the query.
For example
Would use the
filtered_artworks
query routes, but if you had something like:It would handle the query on a different route, perhaps
api/v1/gene/artworks
for example.The tricky thing may be making sure responses conform to the same query shape afterwards. Additional context in slack.
The text was updated successfully, but these errors were encountered: