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

Remove the registry interface and improve plugin interface code quality #119

Merged
merged 2 commits into from
Feb 3, 2025

Conversation

onevcat
Copy link
Member

@onevcat onevcat commented Feb 3, 2025

As noted in issue #118, Flutter has completely removed the PluginRegistry interface from the engine codebase (see flutter/engine#52022). This means that in the next stable release, possibly as soon as version 3.28.0, any code using PluginRegistry will fail to compile.

Given that the PluginRegistry API was deprecated years ago and that nearly all users should now be using the v2 plugin interface, it seems quite safe to remove this from our codebase as well.

Strictly speaking, this type of change should result in a major version update since it introduces breaking changes. However, it appears that Flutter itself isn't adhering strictly to this convention. Therefore, we plan to release this change in the next minor version as well.

@onevcat onevcat requested a review from YkSix February 3, 2025 03:13
Copy link
Contributor

@YkSix YkSix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks.

@onevcat onevcat merged commit e252408 into master Feb 3, 2025
2 checks passed
@onevcat onevcat deleted the fix/remove-registry branch February 4, 2025 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants