Enable configurable `solc --allow-paths` to accomodate non-standard imports
See original GitHub issueThe --truffle
mode is unpleasant to work with, as it creates a huge amount of output. Source mappings are currently also much better when first applied to solidity files.
A more flexible option would be to create a config file like .mythrilrc
, which would allow me to specify path mappings, similar to solc --allow-paths
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Import Path Resolution — Solidity 0.8.17 documentation
Paths used in imports must work the same way everywhere while the command-line ... Additional directories can be whitelisted using the --allow-paths option....
Read more >Solidity Documentation - Read the Docs
Solidity is an object-oriented, high-level language for implementing smart contracts. Smart contracts are programs which govern the behaviour of accounts ...
Read more >solc compiler --allow-paths fails - Ethereum Stack Exchange
I have a folder structure for storing the .sol files, the input JSON, and the compiled JSON output. No matter what variation I...
Read more >flexcel-conceptual-docs-net.pdf - TMS Software
Or only allow paths that are children of the path of the main file, or maybe paths from an allowed list of paths....
Read more >Format of solr.xml | Apache Solr Reference Guide 8.6.1
This section will describe the default solr.xml file included with Solr and how to modify it for your needs. For details on how...
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 FreeTop 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
Top GitHub Comments
For developers, mythril-cli will be superseded by mythjs, so I’ll make this part of the mythjs specs.
Assuming there is still interest in this being used as part of the dev process, rather than just auditing, I think a config file would be much better. That would simplify IDE integrations, and align with tools like linters, truffle, and scripting via NPM.