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.

Sign up for GitHub

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

Jump to bottom

docs: Support for overriding endorsed plugin implementations #10891

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

docs: Support for overriding endorsed plugin implementations #10891

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions src/content/packages-and-plugins/developing-packages.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,10 +186,16 @@ If you can't, for whatever reason, get your implementation
added by the original plugin author, then your plugin
is _not_ endorsed. A developer can still use your
implementation, but must manually add the plugin
to the app's pubspec file. So, the developer
must include both the `foobar` dependency _and_
the `foobar_windows` dependency in order to achieve
full functionality.
to the app's `pubspec.yaml` file:

```yaml
dependencies:
foobar: ^1.0.0
foobar_windows: ^1.0.0 # Non-endorsed plugin implementation
```

This approach also works for overriding an already
endorsed plugin implementation of `foobar`.

For more information on federated plugins,
why they are useful, and how they are
Expand Down
Loading