This repository was archived by the owner on Feb 22, 2023. It is now read-only.
[tool] Clean up "plugin" references #6503
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Historically the tooling was written for plugins, and then was later extended to packages in general. We've done some incremental fixup over time as parts of the tooling were modified, but there are still random references to "plugin" where we actually mean "package", which can be confusing to maintainers of the code (and in the case of the
publish-plugin
command, andlist
types, to tool clients).This is the result of auditing references to "plugin" and fixing the ones that were incorrect.
(It is still the case that most tests use
createFakePlugin
when they could use the newercreateFakePackage
; I fixed a few of those but then realized that the change would be enormous if I continued, and those are pretty harmless, so I left the rest.)Pre-launch Checklist
dart format
.)[shared_preferences]
pubspec.yaml
with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.md
to add a description of the change, following repository CHANGELOG style.///
).