We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I expect that the errors and warnings given are in the source file I am editing, not in a copy that is deleted every run.
Whenever an issue is risen by compiler or Crytic, it points to a file inside .embark/, which leads to mistakes, such as editing the file that is going to be deleted with no warning, or missing links, such as in https://crytic.io/status-im/ens-usernames/8/security_checks/t89Csx2FRb6eJLGq9ERQMQ
Don't make exact copy of the files to then compile them, use the files the user is using.
OS: Linux Embark Version: 6 Node Version: NPM Version:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug Report
Summary
I expect that the errors and warnings given are in the source file I am editing, not in a copy that is deleted every run.
Current behavior
Whenever an issue is risen by compiler or Crytic, it points to a file inside .embark/, which leads to mistakes, such as editing the file that is going to be deleted with no warning, or missing links, such as in https://crytic.io/status-im/ens-usernames/8/security_checks/t89Csx2FRb6eJLGq9ERQMQ
Expected behavior
Don't make exact copy of the files to then compile them, use the files the user is using.
Please provide additional information about your system
OS: Linux
Embark Version: 6
Node Version:
NPM Version:
The text was updated successfully, but these errors were encountered: