Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Follow imports
See original GitHub issueNow I get errors from imported fields:
From:
import "currency.proto";
It would be awesome if those import types are also imported.
Issue Analytics
- State:
- Created 7 years ago
- Comments:28 (11 by maintainers)
Top Results From Across the Web
Running mypy and managing imports
Missing imports#. When you import a module, mypy may report that it is unable to follow the import. This can cause errors that...
Read more >Mypy won't follow imports to local files. " cannot find ... - GitHub
An alternative solution is to add a __init__.py file to the directory. This indicates that the directory is a python module.
Read more >Importing and Exporting | USAGov
But, for certain goods being imported, some agencies may require a license, permit, or other certification. Follow this checklist to avoid ...
Read more >5. The import system — Python 3.11.1 documentation
The import statement is the most common way of invoking the import machinery, ... For example, the following file system layout defines a...
Read more >Is there a way to follow requires or imports for example in ...
Is there a way to follow requires or imports for example in neovim. In my init.lua theres links to other folders for specific...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If you open the proto directory alone, no problem. If proto is not the root directory, it needs to be explicitly specified in the vs configuration. Then restart the editor just fine. Please refer to “protoc”: { “path”: “/usr/local/bin/protoc”, “options”: [ “–proto_path=${workspaceRoot}/common/proto”, ] }
I have the same problem. Both files are in the same folder. They compile fine using protoc on the command line.