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

docs: Support for overriding endorsed plugin implementations #10891

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Gustl22
Copy link
Contributor

@Gustl22 Gustl22 commented Jul 14, 2024

DRAFT: It should may land only after the next major release, when functionality is available in stable.

Description of what this PR is changing or adding, and why:

It is now possible to override native or Dart endorsed plugin implementations. This should be reflected in the docs.

Issues fixed by this PR (if any):

flutter/flutter#80374, flutter/flutter#59657, flutter/flutter#137040
See also: flutter/flutter#80374 (comment)

PRs or commits this PR depends on (if any):

Presubmit checklist

  • This PR is marked as draft with an explanation if not meant to land until a future stable release.
  • This PR doesn’t contain automatically generated corrections (Grammarly or similar).
  • This PR follows the Google Developer Documentation Style Guidelines — for example, it doesn’t use i.e. or e.g., and it avoids I and we (first person).
  • This PR uses semantic line breaks of 80 characters or fewer.

@sfshaza2
Copy link
Contributor

/gcbrun

@flutter-website-bot
Copy link
Collaborator

Visit the preview URL for this PR (updated for commit ee666a2):

https://flutter-docs-prod--pr10891-docs-override-plugins-hpohnkay.web.app

@sfshaza2
Copy link
Contributor

sfshaza2 commented Aug 5, 2024

@Gustl22, any reason we can't take this out of draft form and land it? (After a proper review, that is.)

@Gustl22
Copy link
Contributor Author

Gustl22 commented Aug 6, 2024

@sfshaza2 in the issue description it says in the checklist:
This PR is marked as draft with an explanation if not meant to land until a future stable release.

And I wrote: DRAFT: It should may land only after the next major release, when functionality is available in stable.

I don't know the process. But if this doc is merged and published before the actual feature is released in stable, it may confuses some people as it's not available yet. Otherwise we can mark it as ready and review / merge.

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