fix(typescript-estree): better handle canonical paths #1111
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.
Whilst investigating #1110, I found that there are some cases where typescript will give us their "canonical path" instead of the actual path.
This is a problem on unix because the canonical path is all lower case, which means we can fail to fire directory updates, because the watcher path doesn't match.
This PR adds a pseudo-nominal type (waiting for the day typescript adds it for real) which ensures (at typecheck time) that the canonical path passed in where required.