Dariusz Kuc
02/14/2023, 10:59 PMAleksei Tirman [JB]
02/15/2023, 12:26 PMDariusz Kuc
02/15/2023, 4:21 PMAleksei Tirman [JB]
02/20/2023, 12:00 PMRoute
type receiver, to give the users ability to call it in any place in the routing. Inside that method, you can acquire an instance of your GraphQL
plugin to configure the routes using the GraphQLConfiguration
.Dariusz Kuc
02/24/2023, 8:52 PMinstall(Authentication) {
// configuration
}
install(Routing) {
authenticate(<config>) {
// route config
}
Aleksei Tirman [JB]
02/24/2023, 9:08 PMDariusz Kuc
02/24/2023, 9:10 PMApplicationCall#attributes
? or is there some better wayAleksei Tirman [JB]
02/24/2023, 9:13 PMcall.application.plugin(<PluginClass>)
Dariusz Kuc
02/24/2023, 9:13 PMinstall(GraphQL) {
// config
}
install(Routing) {
graphQLRoute() // <-- requires explicit user config
graphiQLRoute()
}
Aleksei Tirman [JB]
02/24/2023, 9:16 PMDariusz Kuc
02/24/2023, 9:16 PMAleksei Tirman [JB]
02/24/2023, 9:17 PMDariusz Kuc
02/24/2023, 9:17 PMContentNegotiation
globally by
pipeline.install(ContentNegotiation) {
jackson(streamRequestBody = config.server.streamingResponse) {
apply(config.server.jacksonConfiguration)
}
}
but this was breaking users who wanted to use different content negotiation on some other routesAleksei Tirman [JB]
02/24/2023, 9:20 PMContentNegotiation
plugin into specific routesDariusz Kuc
02/24/2023, 9:20 PM