Closed EvanHahn closed 2 months ago
This mainly applies to enums. The main issue to deal with is future attachment types.
A quick look through the existing codebase and I'm not sure if there's anything that stands out as needing changes to account for this right now. The only potential one is maybe this, but this is done at the query level, so not sure if that strictly needs changing for now.
If someone is on a newer version of the schema, we shouldn't error unless it's backwards-incompatible.
For example, if there's a new field on
Observation
that we don't recognize, we shouldn't error.