Skip to content
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

Rename DEPRECATED_HIERARCHICAL_SCOPE_STRATEGY #1760

Closed
aeneasr opened this issue Mar 15, 2020 · 3 comments
Closed

Rename DEPRECATED_HIERARCHICAL_SCOPE_STRATEGY #1760

aeneasr opened this issue Mar 15, 2020 · 3 comments
Assignees
Labels
feat New feature or request. package/oauth2
Milestone

Comments

@aeneasr
Copy link
Member

aeneasr commented Mar 15, 2020

Is your feature request related to a problem? Please describe.

There are no plans to deprecate this strategy, hence it should be renamed to HIERARCHICAL_SCOPE_STRATEGY. The old value should be an alias.

@aeneasr aeneasr added feat New feature or request. package/oauth2 labels Mar 15, 2020
@aeneasr aeneasr added this to the v1.4.0 milestone Mar 15, 2020
@aeneasr aeneasr self-assigned this Mar 15, 2020
@aeneasr aeneasr modified the milestones: v1.4.0, v1.5.0 Apr 23, 2020
@aeneasr aeneasr modified the milestones: v1.5.0, v1.6.0 Jul 1, 2020
@aeneasr aeneasr modified the milestones: v1.6.0, v1.8.0 Aug 4, 2020
@github-actions
Copy link

I am marking this issue as stale as it has not received any engagement from the community or maintainers in over half a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas how you could contribute towards resolving it;
  • open a new issue with updated details and a plan on resolving the issue.

We are cleaning up issues every now and then, primarily to keep the 4000+ issues in our backlog in check and to prevent maintainer burnout. Burnout in open source maintainership is a widespread and serious issue. It can lead to severe personal and health issues as well as enabling catastrophic attack vectors.

Thank you for your understanding and to anyone who participated in the issue! 🙏✌️

If you feel strongly about this issues and have ideas on resolving it, please comment. Otherwise it will be closed in 30 days!

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Sep 21, 2021
@aeneasr
Copy link
Member Author

aeneasr commented Sep 21, 2021

Marked in error.

@aeneasr aeneasr removed the stale Feedback from one or more authors is required to proceed. label Sep 21, 2021
@aeneasr aeneasr modified the milestones: v1.11, v2.0 Oct 13, 2021
@aeneasr
Copy link
Member Author

aeneasr commented May 13, 2022

Done in v2

@aeneasr aeneasr closed this as completed May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request. package/oauth2
Projects
None yet
Development

No branches or pull requests

1 participant