feat(Misc): Expose the storage layout at the contract artifact level #5947
Comments
This was referenced Apr 23, 2024
LHerskind
added a commit
that referenced
this issue
Apr 24, 2024
Fixes #5947 and includes the notes as well. The notes was part of the contract object, but not directly exposed on the artifact itself. Needed to fix a few additional things to make it work: - The `deploy_contract` function was broken (old call flow), it cannot do the new flow because that would be a circular dependency. - Using the `storageLayout` values to get the `storageSlot` that we are using in multiple tests - Using the `notes` values to get the `noteTypeId` that we are using in multiple tests - Removed `lodash.uniqby` as the dependency was not needed after this.
TomAFrench
pushed a commit
that referenced
this issue
Apr 24, 2024
Fixes #5947 and includes the notes as well. The notes was part of the contract object, but not directly exposed on the artifact itself. Needed to fix a few additional things to make it work: - The `deploy_contract` function was broken (old call flow), it cannot do the new flow because that would be a circular dependency. - Using the `storageLayout` values to get the `storageSlot` that we are using in multiple tests - Using the `notes` values to get the `noteTypeId` that we are using in multiple tests - Removed `lodash.uniqby` as the dependency was not needed after this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expose the storage layout on the
ContractArtifactsuch that it can easily be accessedThe text was updated successfully, but these errors were encountered: