You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having a warning from a package, no line or file is indicated. However, this package can be imported in hundreds of different of files. It would be great to have the line and file where the package with the warning has been imported.
Here are some warning (with no indication about position of the import) :
I may want to do something about this package, however I don't remember where I have imported it ... so i have to look for every file or download the zip of the project and do a grep on it.
This issue may be fixed by having a global search utility for a project (right now I think we can only search one file at a time).
Use Case
Having a big project where multiple files imports dependencies. Fixing a warning demands to know where a package is imported.
The text was updated successfully, but these errors were encountered:
Not per se, but the way the web app and the compiler present diagnostics are sufficiently different that the right solution for one isn't necessarily the right one for the other.
Description
When having a warning from a package, no line or file is indicated. However, this package can be imported in hundreds of different of files. It would be great to have the line and file where the package with the warning has been imported.
Here are some warning (with no indication about position of the import) :
I may want to do something about this package, however I don't remember where I have imported it ... so i have to look for every file or download the zip of the project and do a
grep
on it.This issue may be fixed by having a global search utility for a project (right now I think we can only search one file at a time).
Use Case
Having a big project where multiple files imports dependencies. Fixing a warning demands to know where a package is imported.
The text was updated successfully, but these errors were encountered: