Skip to content

Handle strict flag when writing tsbuildinfo - #44394

Merged
Sheetal Nandi (sheetalkamat) merged 3 commits into
mainfrom
strictFlag
Jun 3, 2021
Merged

Handle strict flag when writing tsbuildinfo#44394
Sheetal Nandi (sheetalkamat) merged 3 commits into
mainfrom
strictFlag

Conversation

@sheetalkamat

Copy link
Copy Markdown
Member

Fixes #44305

@sheetalkamat

Copy link
Copy Markdown
Member Author

TypeScript Bot (@typescript-bot) pack this

@typescript-bot

TypeScript Bot (typescript-bot) commented Jun 2, 2021

Copy link
Copy Markdown
Contributor

Heya Sheetal Nandi (@sheetalkamat), I've started to run the tarball bundle task on this PR at d3b479e. You can monitor the build here.

@sheetalkamat

Copy link
Copy Markdown
Member Author

Daniel Rosenwasser (@DanielRosenwasser) we probably need this patch for 4.3 ?

@amcasey Andrew Casey (amcasey) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I get it, but please see my comment.

Comment thread src/compiler/builder.ts Outdated
Comment thread src/compiler/builder.ts Outdated
Comment on lines +567 to +568
// Though this affects semantic diagnostics, affectsSemanticDiagnostics is not set here
// The value of each strictFlag depends on own strictFlag value or this and never accessed directly.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kind of wonder whether it's just worth it to say this always has affectsSemanticDiagnostics set to true since it's unlikely that you'd toggle this but have no difference in effective strict options.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its better that we dont update unnecessarily so prefer to keep it like this. But not stuck on it so open to changing that if you feel strongly about it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What’s the actual consequence of doing it like this? Like if someone had every individual strict flag enabled, and then toggled strict itself, we would be able to correctly identify that it had no effect?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct.

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
@sheetalkamat

Copy link
Copy Markdown
Member Author

TypeScript Bot (@typescript-bot) pack this

@typescript-bot

TypeScript Bot (typescript-bot) commented Jun 2, 2021

Copy link
Copy Markdown
Contributor

Heya Sheetal Nandi (@sheetalkamat), I've started to run the tarball bundle task on this PR at cee9f40. You can monitor the build here.

@sheetalkamat

Copy link
Copy Markdown
Member Author

TypeScript Bot (@typescript-bot) cherry pick this to release-4.3 branch

@DanielRosenwasser

Copy link
Copy Markdown
Member

TypeScript Bot (@typescript-bot) cherry pick this to release-4.3

@DavidZidar

Copy link
Copy Markdown

Sheetal Nandi (@sheetalkamat) Daniel Rosenwasser (@DanielRosenwasser) Looks like you need a dash in "cherry-pick" for the bot to activate

@sheetalkamat

Copy link
Copy Markdown
Member Author

TypeScript Bot (@typescript-bot) cherry-pick this to release-4.3

@typescript-bot

TypeScript Bot (typescript-bot) commented Jun 4, 2021

Copy link
Copy Markdown
Contributor

Heya Sheetal Nandi (@sheetalkamat), I've started to run the task to cherry-pick this into release-4.3 on this PR at cee9f40. You can monitor the build here.

@typescript-bot

Copy link
Copy Markdown
Contributor

Hey Sheetal Nandi (@sheetalkamat), I've opened #44431 for you.

TypeScript Bot (typescript-bot) pushed a commit to typescript-bot/TypeScript that referenced this pull request Jun 4, 2021
Component commits:
b6754e4 Add test showing how setting strict is not preserved in tsbuildinfo Test for microsoft#44305

d3b479e Handle strict flag when writing tsbuildinfo Fixes microsoft#44305

cee9f40 Apply suggestions from code review
Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
Sheetal Nandi (sheetalkamat) added a commit that referenced this pull request Jun 4, 2021
Component commits:
b6754e4 Add test showing how setting strict is not preserved in tsbuildinfo Test for #44305

d3b479e Handle strict flag when writing tsbuildinfo Fixes #44305

cee9f40 Apply suggestions from code review
Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>

Co-authored-by: Sheetal Nandi <shkamat@microsoft.com>
@microsoft Microsoft (microsoft) locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incremental builds with .tsbuildinfo-files are not faster than non incremental builds

6 participants