You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
087e853c5d
Prior to this commit, launching a GraphQL application without any schema file or customizer bean would result in an exception caught by a FailureAnalyzer telling the developer about configured locations. Since then, a new client has been introduced in Spring GraphQL and the mere presence of the GraphQL starter does not mean anymore that the intent is to create a GraphQL API in the app: we could instead just consume an existing, remote API. This commit refines the GraphQL server auto-configuration so that it is enabled only if: * there is at least one schema file in the configured locations * or a `GraphQlSourceCustomizer` bean has been defined in the app These changes make the custom FailureAnalyzer useless and is also removed as part of this commit. Closes gh-30035 |
3 years ago | |
|---|---|---|
| .. | ||
| spring-boot | 3 years ago | |
| spring-boot-actuator | 3 years ago | |
| spring-boot-actuator-autoconfigure | 3 years ago | |
| spring-boot-autoconfigure | 3 years ago | |
| spring-boot-cli | 3 years ago | |
| spring-boot-dependencies | 3 years ago | |
| spring-boot-devtools | 3 years ago | |
| spring-boot-docs | 3 years ago | |
| spring-boot-parent | 3 years ago | |
| spring-boot-properties-migrator | ||
| spring-boot-starters | 3 years ago | |
| spring-boot-test | 3 years ago | |
| spring-boot-test-autoconfigure | 3 years ago | |
| spring-boot-tools | 3 years ago | |