We recently consolidated multiple Angular 16 projects into one NX mono repository using Angular 17. Everything is functioning properly, EXCEPT we have noticed a peculiar change in behavior with our models. Previously, unset properties were simply not displayed at all... but now, they are explicitly marked as "undefined". This can occasionally lead to issues when interacting with HTTP APIs because they interpret this "undefined" as an actual value...
Pre-migration example:
https://i.sstatic.net/MBSV0K0p.png
Post-migration example:
https://i.sstatic.net/J5SlHE2C.png
I am considering making a change in TypeScript like
{
"compilerOptions": {
"strictPropertyInitialization": true
}
}
However, all values are currently set to false... (and it's a compilation setting) My question is.. what could have triggered this shift in behavior?
Edit : I was able to replicate the new behavior in the same mono repo but with Angular 16. Therefore, it doesn't seem to be linked to Angular 17. It might still be due to a new version of TypeScript or a global configuration update.. I just can't pinpoint which one.