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 Provider/Notifier/AsyncNotifier #3947

Open
rrousselGit opened this issue Jan 21, 2025 · 2 comments
Open

Rename Provider/Notifier/AsyncNotifier #3947

rrousselGit opened this issue Jan 21, 2025 · 2 comments
Assignees
Labels
breaking enhancement New feature or request

Comments

@rrousselGit
Copy link
Owner

In 3.0, some classes will likely be renamed:

Provider > SyncProvider
Notifier > SyncNotifier
AsyncNotifierProvider > FutureNotifierProvider
AsyncNotifier > FutureNotifier
ProviderBase > Provider
NotifierBase > Notifier

This removes the weird Base in the name of some abstract classes.

And it aligns FutureProvider and AsyncNotifier ; similarly to how we have StreamProvider and StreamNotifier.

@rrousselGit rrousselGit added breaking enhancement New feature or request labels Jan 21, 2025
@rrousselGit rrousselGit self-assigned this Jan 21, 2025
@rrousselGit
Copy link
Owner Author

Provider>SyncProvider and the Notifier variant are not necessary btw.
If we also do #3904 then it's find to keep Provider as is.

But I think it's important to rename AsyncNotifier to FutureNotifier

@rrousselGit
Copy link
Owner Author

In case it wasn't obvious, we'd have a migration command. Possibly using dart fix itself if I manage to use it. Otherwise a custom one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant