TIL that in TypeScript, if you define a class with readonly properties and an empty constructor, TypeScript will automatically assign the properties to the class.

Not sure if I love that, tbh, since I was under the impression that TS tends to not modify logic...

Staff Eng at Iron Fish • Building BlockSocks 🧦

maybe they are encouraging people to not use `class` by sprinkling scary magic there! 😅🥹

Same deal for `public name` / `private name` / `protected name`. Pretty sure they did it this way so you don’t have to repeat the same definitions in the class body.

Downside of this shorthand is you’re limited to using single ordered arguments in the constructor.

Same deal for `public name` / `private name` / `protected name`. Pretty sure they did it this way so you don’t have to repeat the same definitions in the class body.

Downside of this shorthand is you’re limited to using single ordered arguments in the constructor.

https://www.typescriptlang.org/play/?#code/MYGwhgzhAEAqAWBLAdgc2gbwFAEhgHtkIAXAJwFdhj9SAKXHAB1P2IFMq2ATaMALmglSKVABoGjcgCMQiYNCkChI8TibCAbmHbRgSsitwBKTFlwBfLOaA

This isn't logic modification, as the `readonly` is only a part of TS's type system. There's no `readonly` in JS. So, stick your prev. assumptions on *logic modification* of TS.

Interesting feature in TypeScript! It's important to be aware of such automatic assignments to ensure it aligns with your intended logic. TypeScript can be quite helpful but it's always good to double-check to avoid unexpected behavior.