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

Introduce @ToBeReplacedByLazyProperty annotation #29178

Closed
asodja opened this issue May 16, 2024 · 0 comments · Fixed by #29235
Closed

Introduce @ToBeReplacedByLazyProperty annotation #29178

asodja opened this issue May 16, 2024 · 0 comments · Fixed by #29235
Labels
a:chore Minor issue without significant impact in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty p:lazy-migration Issues covered by migration to an all-lazy API
Milestone

Comments

@asodja
Copy link
Member

asodja commented May 16, 2024

We would like to mark properties that will be migrated to lazy so we can get better overview of them. Let's introduce ToBeReplacedByLazyProperty or @WillBecomeLazy or something like that.

Annotation should also have blockedBecause and blockedIssue so we can mark there are some blockers for the migration.

@asodja asodja added a:feature A new functionality in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty p:lazy-migration Issues covered by migration to an all-lazy API labels May 16, 2024
@asodja asodja changed the title Introduce @ToBeUpgraded annotation Introduce @ToBeReplacedByLazyProperty annotation May 21, 2024
@asodja asodja added a:chore Minor issue without significant impact and removed a:feature A new functionality labels May 22, 2024
@bot-gradle bot-gradle added this to the 8.9 RC1 milestone May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:chore Minor issue without significant impact in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty p:lazy-migration Issues covered by migration to an all-lazy API
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants