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
cmd/ctrl-click on import identifier doesn't work on npm packages #402
Comments
@openzeppelin/contracts
Are you sure that the "import x from x" statement is correct? Does the solidity support the grammar? |
Yes, I'm 100% sure it is supported, otherwise it would complain about compilation errors. Not sure why you referenced a 3rd party docs that may not have the complete set of rules. Please see https://docs.soliditylang.org/en/latest/layout-of-source-files.html for the official reference, thank you 🙏 |
@jonahcui That looks like just the docs for that file, what happens when you cmd+click on the text between the {} ? The expected behaviour is that it should jump to the file with scrollbar targeted at the class name. |
It will jump to the code source.
2023年9月15日 +0800 17:10 Van Nguyen ***@***.***>,写道:
… @jonahcui That looks like just the docs for that file, what happens when you cmd+click on the text between the {} ? The expected behaviour is that it should jump to the file with scrollbar targeted at the class name.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi there, Looks like you have a problem with the external imports, please consider these 2 things:
Btw if the compiler is doing well, the extension also should work Also the problem doesn't seem to be general, as it is Ok now on my system (current new version by the time of submitting this response) ! Good Luck |
For example:
cmd-click doesn't work when clicking on
{Initializable}
or{IERC20}
, but it works for local files in the example{Ownable}
. cmd-click on the filePath is fine though, to make sure that the file actually exists.The text was updated successfully, but these errors were encountered: