Skip to content

Separate transports in GraphQL auto-configuration #44495

New issue
New issue
Closed
Closed
Separate transports in GraphQL auto-configuration#44495
Assignees
bclozel
Labels
type: enhancementA general enhancement
Milestone
 
3.5.0-M3
@bclozel

Description

@bclozel
bclozel
opened on Feb 28, 2025
Member

As discussed in spring-projects/spring-graphql#1124, the current auto-configuration mixes a bit configuration properties and beans for different transports and layers.

We should revisit our auto-configuration to:

  • move configuration properties into dedicated transport namespaces
  • refine the dependencies between the core auto-configuration and the transport auto-configurations

Activity

bclozel
added
type: enhancementA general enhancement
on Feb 28, 2025
bclozel
added this to the 3.5.0-M3 milestone on Feb 28, 2025
bclozel
self-assigned this
on Feb 28, 2025
bclozel
closed this as completedin 83f678aon Feb 28, 2025
bclozel
mentioned this on Feb 28, 2025
pull
added a commit that references this issue on Feb 28, 2025

Separate transports in GraphQL auto-configurations

83f678a
snicoll
mentioned this on May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @bclozel

      Issue actions
        Separate transports in GraphQL auto-configuration · Issue #44495 · spring-projects/spring-boot