Closed sir-captainmorgan21 closed 2 years ago
Hmmm.. interesting. I'll take a look as soon as I can
So it looks like this is an issue with the Nx CLI. It's not reading the defaults in the version you have installed (which was the same version Nx Console uses, so it happens here too 😅 ).
Upgrading to the latest version should have this issue fixed.
@Cammisuli are you bumping to the latest NX version in NX Console? Do we need to follow suite?
I'll update Nx Console eventually, but you should update on your schedule.
For context, the version that Nx Console uses doesn't matter in this case because at this point we just call the locally installed Nx cli, with the modified values that were in the form. Nx itself didn't read the defaults.
Current Behavior
We have default nx.json schematic settings defined like so.
When using NX Console to run one of these generators, the defaults are populated in the form, but they aren't honored in the actual run of the generator. See below where
style
is set tonone
but it is still creating a .css file. Even if I changed it to another option and then back to "none", it will honor the other option (IE: scss), but not honor the "none". If I go remove that configuration in nx.json, the "none" option, along with the other previously defaulted options work fine.Expected Behavior
NX Console run should honor default settings.
Steps to Reproduce
Steps to reproduce are covered in description of bug.
Failure Logs / Images / Videos
Nothing "fails"
Environment