Skip to content

Conversation

quaff
Copy link
Contributor

@quaff quaff commented Sep 9, 2025

  1. Deprecate field role in favor of authority since role is specific authority.
  2. Add Javadoc to state that role should be prefixed.

@rwinch
Copy link
Member

rwinch commented Sep 9, 2025

Can you elaborate on why you want to make this change? Given that role is internal, I don't see a lot of value making a breaking change.

@rwinch rwinch added status: waiting-for-feedback We need additional information before we can continue and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 9, 2025
@rwinch rwinch self-assigned this Sep 9, 2025
@rwinch rwinch added in: core An issue in spring-security-core type: breaks-passivity A change that breaks passivity with the previous release labels Sep 9, 2025
@quaff
Copy link
Contributor Author

quaff commented Sep 10, 2025

Can you elaborate on why you want to make this change? Given that role is internal, I don't see a lot of value making a breaking change.

I'm confused by the name while reading the source, I force pushed a commit, it's not a breaking change now.
I'm OK to revert the code changes, but I think it's valuable to improve Javadoc to elaborate why the name must be role not authority, and if the authority is a role it should be prefixed.

@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue labels Sep 10, 2025
1. Deprecate field `role` in favor of `authority` since role is specific authority.
2. Add Javadoc to state that role should be prefixed.

Signed-off-by: Yanming Zhou <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core An issue in spring-security-core status: feedback-provided Feedback has been provided type: breaks-passivity A change that breaks passivity with the previous release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants