Conversation
732f435 to
ec14852
Compare
| await fs.remove(dir); | ||
| } else { | ||
| const timestampText = await fs.readFile(timestampFile, 'utf8'); | ||
| const timestampText = await fs.readFile(timestampFile, "utf8"); |
Check failure
Code scanning / CodeQL
Potential file system race condition
aeisenberg
left a comment
There was a problem hiding this comment.
I think this looks good to me, though others should take a look to be sure.
|
Do we need to update any CONTRIBUTING guidelines? |
I don't think so. We are not currently mentioning tsfmt or ESLint at all in the CONTRIBUTING guidelines and probably assume those will be caught automatically by the |
7cb044c to
9a07f2f
Compare
9a07f2f to
91c3d3d
Compare
This adds Prettier and makes it replace tsfmt. VSCode is set to use Prettier for formatting TypeScript/TSX files and format on save since Prettier is very fast and does not cause any noticeable delay.
This will change all existing files to match Prettier formatting. The command used is `npm run format`.
91c3d3d to
f515663
Compare
|
Can we ignore the "Code scanning results / CodeQL" check? It seems like the vulnerability it detects is already present in the code and this PR just moves the code, so it isn't introducing a new vulnerability. |
Yep, should be fine to just ignore it. Thankfully the check isn't required. I agree it's just code moving around and not actually new alerts. |
This adds Prettier and replaces tsfmt. VSCode is set to use Prettier for formatting TypeScript/TSX files and format on save since Prettier is very fast and does not cause any noticeable delay.
I've changed some of the default configuration of Prettier so we have less changes, but there are still many changes in formatting in almost all files. It's best to review this PR commit-by-commit: the second commit just runs
npm run formatand does not have any manual changes.Checklist
ready-for-doc-reviewlabel there.