Don't rely on Schema->exists() in Build
Don't rely on Schema->exists() in Build

Schema->exists() *only* works when processTypes() has been called,
which only happens during save(). Checking for exists() beforehand
will just silently fail to build the schema.

This wasn't noticed until now because the admin schema defines
custom queries directly, and is not reliant on processTypes to transfer
the inferred queries from ModelType.

Note that there's already a check that you have some queries defined in Schema:
"Your schema must contain at least one type and at least one query".
Which actually kicks in now during save(), after removing the continue statement.

silverstripe/silverstripe-graphql