You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
solidity-flycheck can now detect projects.
Project roots:
When `solidity-flycheck-use-project' is t, solidity-flycheck will detect a project
and include files in the project during compilation and linting. solidity-flycheck
will look for a .soliumrc.json in a parent directory. If found, this directory is
considered the project root. If no .soliumrc.json is found, `project-roots' is used.
When `solidity-flycheck-solium-checker-active' is t, the .soliumrc.json found in
the project root will be used as the solium config, rather than a .soliumrc.json
in the same directory as the file being linted.
When `solidity-flycheck-solc-checker-active' is t, the project root will be passed
to solc using the --allow-paths flag. This means imports to other files inside the
project will lint without erorr."
Additional allow-paths:
The custom variable `solidity-flycheck-solc-additional-allow-paths' can be set to
support additional allow-paths.
This lets you import .sol files from other directories without causing linting errors.
For example, say that you use Brownie (URL `https://github.com/eth-brownie/brownie'),
which stores ethPM packages in \"~/.brownie/packages\". You could add \"~/.brownie/packages\"
to this variable to import ethPM packages without linting errors. Subdirectories
in each allow path are remapped.
Note that when `solidity-flycheck-use-project' is t, the project root will be
added to --allow-paths in addition to any paths defined here.
0 commit comments