Document default tsBuildInfoFile defaults #2733
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I was going to report a bug because the actual default of tsbuildinfo does not match the docs for --tsBuildInfoFile. I found [this issue] was already reported and closed as 'working as intended'. So I decided to add @sheetalkamat's response to the docs. [this issue]: microsoft/TypeScript#30925
sheetalkamat
approved these changes
Mar 1, 2023
jakebailey
reviewed
May 17, 2023
jakebailey
requested changes
May 19, 2023
There was a problem hiding this comment.
Now that #2303 is merged, this will take a little bit of tweaking and merge conflict solving. Happy to look again afterward.
jakebailey
approved these changes
Jul 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was going to report a bug because the actual default of tsbuildinfo does not match the docs for --tsBuildInfoFile. I found this issue was already reported and closed as 'working as intended'.
So I decided to add @sheetalkamat's response to the docs.