How to import contracts in Cadence using flow.json instead of relative paths

Viewed 25

Importing contracts using their relative path is not working atm with the last version of the cadence language server. I was wondering what would be the alternative, when developing locally, for importing other contracts. My best guess is that it should be using the flow.json file, defining the paths for the contracts on it, but I cannot find how to specify on my contract that I want to it to use the config file for the imports

1 Answers
Related