openzeppelin-contract-loader icon indicating copy to clipboard operation
openzeppelin-contract-loader copied to clipboard

Load contract ABIs from built artifacts and return contract objects

Results 9 openzeppelin-contract-loader issues
Sort by recently updated
recently updated
newest added

Bumps [minimist](https://github.com/minimistjs/minimist) and [mkdirp](https://github.com/isaacs/node-mkdirp). These dependencies needed to be updated together. Updates `minimist` from 1.2.5 to 1.2.8 Changelog Sourced from minimist's changelog. v1.2.8 - 2023-02-09 Merged [Fix] Fix long option...

dependencies

Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2. Release notes Sourced from decode-uri-component's releases. v0.2.2 Prevent overwriting previously decoded tokens 980e0bf https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2 v0.2.1 Switch to GitHub workflows 76abc93 Fix issue where decode...

dependencies

Function `dependencyArtifactPath()` is adding hard-coded `build/contracts` to the path already using `artifactsDir` from `loadArtifact()`, failing to load artifacts on test environment. ``` function dependencyArtifactPath(contractWithDependency: string): string { const fragments =...

Bumps [ajv](https://github.com/ajv-validator/ajv) from 6.10.2 to 6.12.6. Release notes Sourced from ajv's releases. v6.12.6 Fix performance issue of "url" format. v6.12.5 Fix uri scheme validation (@​ChALkeR). Fix boolean schemas with strictKeywords...

dependencies

Contract loader is currently designed to have filesystem access to load the artifacts. It would be nice if the same methods for loading artifacts in local tests could also be...

idea

As noted [here](https://github.com/OpenZeppelin/openzeppelin-contract-loader/pull/9#discussion_r360521009), the current API has two optional values that are often mutually exclusive (`bytecode` and `address`), making calling the function at times awkward. Consider splitting this into two...

We are currently setting the unlinked_binary property of truffle contracts when loading it from an artifact. We should test that loading a contract with linked libraries works properly, in both...

In case we implement #5, we could rework the existing `Contracts` class in SDK to use this library instead. If so, it'd be easier to manage if we keep it...

We should provide an interface to load existing deployments (potentially filtered by proxies, minimal proxies, or regular deploys) via contract-loader, by automatically reading the contents of the corresponding network json...

enhancement