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.

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

Support Ape 0.8 #594

Open
antazoey opened this issue Aug 28, 2024 · 2 comments
Open

Support Ape 0.8 #594

antazoey opened this issue Aug 28, 2024 · 2 comments

Comments

@antazoey
Copy link

antazoey commented Aug 28, 2024

Ape 0.8 has a few changes that causes problems when using this VSCode integration, mostly documented here ApeWorX/ape-solidity#152.

  • contracts/.cache is no longer available - it now only exists in a sandbox during compilation. Dependencies are pulled from the root ~/.ape/packages folder at compile time. However, note the names of the packages are folder-style escaped so you have to do some adjustments.
  • remappings 99% of the time are no longer specified in the ape-config.yaml. This is because the auto-remapping feature covers all typical use-cases.

I am not sure if there are additional changes to consider.

One note: Both pre-0.8 and post-0.8 style projects should be supported (ideally). This is because some older projects may not require or intend on updating Ape.

@alcuadrado
Copy link
Member

remappings 99% of the time are no longer specified in the ape-config.yaml. This is because the auto-remapping feature covers all typical use-cases.

Is there a way to print all the remappings, including automatic ones, using ape? We could use that instead.

@antazoey
Copy link
Author

antazoey commented Aug 28, 2024

Is there a way to print all the remappings, including automatic ones, using ape? We could use that instead.

You can like this:

In [1]: compilers.solidity.get_import_remapping()
Out[1]: 
{'@openzeppelin': 'contracts/.cache/openzeppelin/4.5.0',
 'openzeppelin': 'contracts/.cache/openzeppelin/4.5.0'}

Would that work or would a CLI command be required?

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

No branches or pull requests

2 participants