Closed fpaul-1A closed 6 months ago
CI is running/has finished running commands for commit f9a9a3ec07d7d9194a57c80497c3f3ad2b9dcae3. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
Sent with 💌 from NxCloud.
Is it a change in Ng17 that makes the additionalProperty: true
ignored by the CLI option validation process? Or did we have an issue before?
What's about our other schematics that are supposed to propagate the options to the child Angular schematics?
Is it a change in Ng17 that makes the
additionalProperty: true
ignored by the CLI option validation process? Or did we have an issue before? What's about our other schematics that are supposed to propagate the options to the child Angular schematics?
We already have this issue in the current releases We already define all properties for the case of angular components
Is it a change in Ng17 that makes the
additionalProperty: true
ignored by the CLI option validation process? Or did we have an issue before? What's about our other schematics that are supposed to propagate the options to the child Angular schematics?We already have this issue in the current releases
We already define all properties for the case of angular components
I see 😟 Can you then link the issue associated (and/or PR relative to the component and library fix)?
Proposed change
Fix following issue:
Related issues