superfluid-finance / automation-subgraphs Goto Github PK

Why?

• Bring us in line with industry best practice
• Helps us manage bigger protocol subgraph changes with fewer issues
• Better monitoring

GraphQL Mesh shows promise to be used as a gateway for our subgraphs with additional capabilities like schema stitching, schema monitoring, caching, etc. Automation subgraphs are a great place to experiment, as we've currently given out direct links to the GraphQL server hosted on The Graph's hosted service.

What?

Fields like createdAt shouldn't be nullable.

WrapSchedule schema from production (note the no "!" specified for createdAt):

Why?

This is a problem because it makes consumer code unnecessarily handle null values.

How?

Specify as non-null in the subgraph mapping code.