Skip to content

Register indirect fragment introduced by super interfaces #3213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

quaff
Copy link
Contributor

@quaff quaff commented Nov 25, 2024

Fix GH-3212

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Nov 25, 2024
@mp911de mp911de added the for: team-attention An issue we need to discuss as a team to make progress label Nov 28, 2024
@mp911de mp911de added status: on-hold We cannot start working on this issue yet type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 2, 2024
@mp911de mp911de added status: declined A suggestion or change that we don't feel we should currently apply and removed status: on-hold We cannot start working on this issue yet for: team-attention An issue we need to discuss as a team to make progress labels May 9, 2025
@mp911de
Copy link
Member

mp911de commented May 9, 2025

We do not want to introduce additional lookups from super-interfaces.

@mp911de mp911de closed this May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SPI fragment can not be introduced by @NoRepositoryBean
3 participants