Support for remappings

I am using solc’s remapping feature and brownie for my project. Doing either of these cause the vscode-solidity’s plugin to fail loading my imports.

It would be really helpful if there were some sort way to include these remappings in the project’s settings.

https://solidity.readthedocs.io/en/develop/layout-of-source-files.html?#use-in-actual-compilers

For example, if you clone github.com/ethereum/dapp-bin/ locally to /usr/local/dapp-bin, you can use the following in your source file: import "github.com/ethereum/dapp-bin/library/iterable_mapping.sol" as it_mapping; Then run the compiler: solc github.com/ethereum/dapp-bin/=/usr/local/dapp-bin/ source.sol

There’s another plugin that has the feature, but it hasn’t been updated in 2 years.

[juanfranblanco]

@merc-0 it is supported now, also @PatrickAlphaC confirmed in another thread it is working now with Brownie.

[juanfranblanco]

@cameel @PatrickAlphaC @merc-0 @WyseNynja just checked in the initial support. Not perfect yet as it is driven by the global / workspace settings. I think going deeper will takes us back to the project file / module or the old dapp project file 😃. Which can contain each remapping, module / context name etc.

Notes:

• Remapping support included in the workspace / global settings, the remapping base path is relative to the workspace root folder.
• Issues at the moment, multiple folders in a workspace will use the same remapping (as it is a workspace setting and for that folder)
• No support for “context”, so mainly this uses the workspace folder for all dependencies. Solution for this and above will be find the current “remappings.txt” (or project file) in each folder and use that as the Package remapping configuration. Context name (package name, could be driven from that).

Edit: “remappings.txt” is not supported yet (just in case is not clear)