fix: OutputFolder path issue when both output
and dest
properties are specified
#9975
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.
This PR intended to fix issue #8967
Currently when both
output
anddest
properties are specified.It's resolved to
{baseDir}/{output}/{dest}
path.It cause problems when specifying
dest
on config and using--output
parameter.This PR changes this behavior to use
output
if it's specified by config/parameter.And only use the
dest
property if the `output' parameter is not specified.Additionally following changes are included in this PR.
[Obsolete]
attribute todest
property.dest
property. So it shouldn be removed after Json schema validation logics are integrated.dest
property. And add warning suppressions that usedest
property.new TemplateManager
's constructor parameter to usebaseDirectory
(No behavior changes)optionsBaseDirectory
variable and comments.