You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workspace should provide a general plug‐in system to allow custom tasks to be shared across projects.
A standard plug‐in would be a Swift Package which provides an executable.
Plug‐ins would be applied using an addition to the WorkspaceConfiguration so that a user can specify the package URL, version, product, command line arguments, etc.
Plug‐ins would be separately applicable to the refresh, proofread and validate phases.
To start with, plug‐in output should be displayed and success based on the exit code. Tighter integration could be added at a later date.
(This is almost how SwiftLint integration in implemented now. It just needs to generalized and surfaced in the configuration API. As part of implementing this feature, SwiftLint should lose its privileged status and become default plug‐in for the proofread phase.)
The text was updated successfully, but these errors were encountered:
SDGGiesbrecht
added
Implemented
Implemented in a pull request, but not yet merged into the master branch.
and removed
Designed
Design finalized, but not yet implemented.
labels
Apr 2, 2019
SDGGiesbrecht
added
Merged
Implemented in the master branch, but not released yet.
Released
Addressed in a stable release.
and removed
Implemented
Implemented in a pull request, but not yet merged into the master branch.
Merged
Implemented in the master branch, but not released yet.
labels
Apr 3, 2019
Workspace should provide a general plug‐in system to allow custom tasks to be shared across projects.
WorkspaceConfiguration
so that a user can specify the package URL, version, product, command line arguments, etc.(This is almost how SwiftLint integration in implemented now. It just needs to generalized and surfaced in the configuration API. As part of implementing this feature, SwiftLint should lose its privileged status and become default plug‐in for the proofread phase.)
The text was updated successfully, but these errors were encountered: