4 ms·
You point out issues that are already solved. It's a people problem you have now :) no amount of configuration is going to fix that. Also strict has been the d
by PudgePacket 8y ago
You point out issues that are already solved. It's a people problem you have now :) no amount of configuration is going to fix that.
Also strict has been the default for quite a while!
- knocte 8y ago> Also strict has been the default for quite a while! That would prevent anyone to rename a .js file to .ts and compile successfully. Which I think is not the case today. Prove otherwise please.
- PudgePacket 8y agohttps://github.com/Microsoft/TypeScript/commit/d3b7058c2999f68c04278e15cbc29c91bcc44dc5 https://github.com/Microsoft/TypeScript/commit/d3b7058c2999f... over a year.
- WorldMaker 8y agoAlso, the allowJS compiler switch became the preferred approach for in-place migrations over mass renames. It makes it easier to opt in to strict type checking on a file-by-file basis. https://www.typescriptlang.org/docs/handbook/migrating-from-javascript.html https://www.typescriptlang.org/docs/handbook/migrating-from-...