Cache searches for default config files during FAR #48113
Closed
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
It's not unusual for FAR to find more than one result in a given file, but the work of searching the file system for the associated tsconfig.json will only be cached if the file is open (which is frequently not the case for FAR).
typescript-bot
added
Author: Team
For Uncommitted Bug
Member
Author
|
There are so many layers of caching (in this case, the tsconfig-existence cache seems to be the main one) that this has no effect in practice. |
Collaborator
|
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
It's not unusual for FAR to find more than one result in a given file, but the work of searching the file system for the associated tsconfig.json will only be cached if the file is open (which is frequently not the case for FAR).