-
Notifications
You must be signed in to change notification settings - Fork 138
Closed
Labels
InfrastructureIssues for the overall performance plugin infrastructureIssues for the overall performance plugin infrastructure[Plugin] Performance LabIssue relates to work in the Performance Lab Plugin onlyIssue relates to work in the Performance Lab Plugin only[Type] EnhancementA suggestion for improvement of an existing featureA suggestion for improvement of an existing feature
Milestone
Description
This issue is part 1/2 for setting up the new infrastructure for developing standalone plugins.
Requirements
This work should be implemented against a new feature/modules-to-plugins feature branch.
- Create new
pluginsfolder in the repository root. - Add a
.gitkeepto it. - Add the
pluginsfolder to be ignored in.gitattributesso that it won't be part of the Performance Lab plugin build. - Restructure the
plugins.jsonfile:- Going forward, there should be always two top level properties:
modulesandplugins. modulesshould have the map of "module => plugin data (slug and version)", i.e. the same thing that the file contains today.pluginsshould have an array of plugin slugs.
- Going forward, there should be always two top level properties:
- Update the existing workflows that use the
plugins.jsonfile to look for modules within the newmodulesproperty in the file. - Add references to the new
pluginsfolder in any dev tooling that currently lints/covers themodulesfolder (e.g. inphpcs.xml.distetc.).
Note: Additional changes to build/publish the new plugins should be implemented in a separate follow-up issue.
Metadata
Metadata
Assignees
Labels
InfrastructureIssues for the overall performance plugin infrastructureIssues for the overall performance plugin infrastructure[Plugin] Performance LabIssue relates to work in the Performance Lab Plugin onlyIssue relates to work in the Performance Lab Plugin only[Type] EnhancementA suggestion for improvement of an existing featureA suggestion for improvement of an existing feature