fix(schematics): use Angular default properties when not defined #2507
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Closes #1036(comment)
What is the new behavior?
Does this PR introduce a breaking change?
Other information
By removing the default values in the schema, we can remove the undefined values before we pass them to the Angular component schematic. By doing this, Angular will replace the undefined values with the defaults set in
angular.json
. If no default value is provided in theangular.json
file, it will use the defaults from the Angular schematic schema.I tried to write a test for it but it seems like during the tests, the transformer isn't included.