-
Notifications
You must be signed in to change notification settings - Fork 12.8k
🤖 User test baselines have changed #28524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
typescript-bot
wants to merge
1
commit into
microsoft:master
from
typescript-bot:user-update-20181003
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
Exit Code: 1 | ||
Standard output: | ||
src/App.tsx(2,8): error TS2307: Cannot find module './App.css'. | ||
src/components/Hello.tsx(2,8): error TS2307: Cannot find module './Hello.css'. | ||
|
||
|
||
|
||
Standard error: |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!?!? Did something in this project's dependency hierarchy change to no longer include a
css
blanket module declaration? cc @DanielRosenwasserUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahhhhhhhhhhhhhhhhhhhhhhh, I know what it is - we don't have a
*.css
module reference in the starter and never have. And for some reason, we've never validated the paths onImportDeclaration
s with no clauses (because we only do that during export resolution and if you request no members, we do no export resolution). In 7a71887,getAlternativeContainingModules
attempts a lookup of all imports in a file (including ones we don't look at exports for) to try to find aliases of a symbol for printing a better name for it. This causes us to actually check the validity of the import and learn that in fact it is not valid.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DanielRosenwasser didn't that we don't check these kinds of imports come up recently? Do we want to formally fix the behavior and check their validity (like this, but ideally more explicitly), or should I suppress any errors from
resolveExternalModuleName
duringgetAlternativeContainingModules
?