mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-15 17:31:56 +03:00
0c1016e065
Previously invalid REST endpoints would throw errors during schema cache build. This PR changes the validation to instead add to the inconsistent metadata objects in order to allow use of `allow_inconsistent_metadata` with inconsistent REST endpoints. All non-fatal endpoint definition errors are returned as inconsistent metadata warnings/errors depending on the use of `allow_inconsistent_metadata`. The endpoints with issues are then created and return informational runtime errors when they are called. Console impact when creating endpoints is that error messages now refer to metadata inconsistencies rather than REST feature at the top level:  <img width="969" alt="image" src="https://user-images.githubusercontent.com/92299/110258597-8336fa00-7ff7-11eb-872c-bfca945aa0e8.png"> Note: Conflicting endpoints generate one error per conflicting set of endpoints due to the implementation of `groupInconsistentMetadataById` and `imObjectIds`. This is done to ensure that error messages are terse, but may pose errors if there are some assumptions made surrounding `imObjectIds`. Related to https://github.com/hasura/graphql-engine-mono/pull/473 (Allow Inconsistent Metadata (v2) #473 (Merged)) --- ### Kodiak commit message Changes the validation to use inconsistent metadata objects for REST endpoint issues. #### Commit title Inconsistent metadata for REST endpoints GitOrigin-RevId: b9de971208e9bb0a319c57df8dace44cb115ff66 |
||
|---|---|---|
| .. | ||
| actions | ||
| compression | ||
| endpoints | ||
| event_triggers | ||
| explain | ||
| graphql_introspection | ||
| graphql_mutation | ||
| graphql_query | ||
| graphql_validation | ||
| heterogeneous | ||
| horizontal_scale/basic | ||
| inconsistent_objects | ||
| logging | ||
| query_cache | ||
| remote_schemas | ||
| schema/duplication | ||
| subscriptions | ||
| unauthorized_role | ||
| v1 | ||
| webhooks/request_context | ||
| clear_db.yaml | ||
