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
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.
The text was updated successfully, but these errors were encountered:
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.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.
The text was updated successfully, but these errors were encountered: