pylance-release
pylance-release copied to clipboard
Add informational quickfix when an import could not be resolved
Discussed in https://github.com/microsoft/pylance-release/discussions/3297
Originally posted by karrtikr September 6, 2022

During a user study for testing getting started experience, 3 out of 4 users got stuck at this step. They went searching outside the tool (VSCode) on how to resolve the issue, which is when they got lost as they weren't sure if the solution applies to them.
It would be nice if we could provide an internal link here like Typescript does:

about how one can generally resolve these errors. Same as https://github.com/microsoft/pylance-release/issues/2483.
cc/ @cwebster-99 @karthiknadig