Skip to content

.embark/contracts breaks parallel tools, such as Crytic, and it's counter intuitive #2396

Description

@3esmit

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:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions