You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2023. It is now read-only.
When importing some of the starters in a spring-boot application, let's say graphql-kickstart-spring-boot-starter-webflux, some of the autoconfigured beans are marked as @ConditionalOnMissingBean, which is fine if you want to customize something.
The problem is that those bean types classes are placed in runtime-scoped dependencies, so at compile time you won't be able to use them to override or extend some functionalities.
Is that the desired situation? For me it seems cumbersome because you need to copy all dependencies and import them in your project instead of relying on the aforementioned starter
The text was updated successfully, but these errors were encountered:
When importing some of the starters in a spring-boot application, let's say graphql-kickstart-spring-boot-starter-webflux, some of the autoconfigured beans are marked as @ConditionalOnMissingBean, which is fine if you want to customize something.
The problem is that those bean types classes are placed in runtime-scoped dependencies, so at compile time you won't be able to use them to override or extend some functionalities.
Is that the desired situation? For me it seems cumbersome because you need to copy all dependencies and import them in your project instead of relying on the aforementioned starter
The text was updated successfully, but these errors were encountered: