feat(devkit): update parseTargetString
to allow referencing targets on the current project
#19109
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.
Current Behavior
When an executor takes a
buildTarget
option, it frequently is a target on the current project. Currently, folks must reference the full target string, starting with the project. This means that the option is filled in with something like:my-project:build
, even inside ofmy-project
'sproject.json
file.Expected Behavior
When filling in parameters with a
buildTarget
or similar fields, you can omit the project name if referencing a target on the same project.Note
This PR only updates the helper - follow up PRs will be required for each plugin to pass in the executor context instead of the graph.