Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

InternalEVM is not recognized & results in problems within EVM contract #574

Open
sisyphusSmiling opened this issue Mar 25, 2024 · 0 comments
Open

InternalEVM is not recognized & results in problems within EVM contract #574

sisyphusSmiling opened this issue Mar 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@sisyphusSmiling
Copy link

sisyphusSmiling commented Mar 25, 2024 •
edited
Loading

Problem

EVM contract runs into errors on InternalEVM calls and cannot be used in dependent contracts without also propagating those syntax errors
cannot find variable in this scope: InternalEVM. not found in this scope

Steps to Reproduce

Open a project with the EVM contract, dependencies and properly configured flow.json (see flow-evm-bridge) and notice syntax highlighting raises errors on InternalEVM within the EVM contract. Also look for checking of imported program EVM failed wherever EVM is imported.

Acceptance Criteria

EVM contract is supported by Cadence VSCode extension

Context

Flow VM bridge. Not a blocker.

CLI version: v1.15.0-cadence-v1.0.0-preview.13
Extension version: v2.3.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
🌊 Flow 4D
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sisyphusSmiling