fix(project): runTaskCommand()
ignores projenCommand
#3293
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.
The existing implementation of
runTaskCommand()
onProject
has a bug that is causing it ignore the value ofprojenCommand
.While looking at fixing this, I noticed a bunch of inconsistency in this area. For example
NodeProject
has its own implementation ofrunTaskCommand()
andNodePackage
has a customprojenCommand
, which I deprecated. There's also some inconsistency of whenprojenCommand
is used directly vs. whenrunTaskCommand()
is used and both have a different default value.I don't have time to sort out this mess right now, because both "easy fixes" have some wider implications:
npx projen@<version>
the default forprojenCommand
feels safer, but would cause all generated files to update the header all the timenpx projen
inrunTaskCommand()
seems less safe for languages that don't have the projen version locked in a lockfile.Thus I have focused on fixing the bug at hand. This is a low hanging fruit albeit the implementation is a bit akward.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.