Cairo: Support ERC-6909 extensions#793
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThe PR adds three new optional features to the ERC6909 token standard: contentUri for contract/token URI metadata, tokenSupply for tracking total supply per token ID, and metadata for per-token metadata fields (name, symbol, decimals). These options are integrated throughout the Cairo Alpha implementation, including core logic, code generation, test coverage, UI controls, and AI function definitions. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsTimed out fetching pipeline failures after 30000ms Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts (1)
63-89: Add one non-upgradeablecontentUri/metadatacase.Every new extension scenario here either keeps
upgradeableon or opts into explicit roles, so this file still never exercises the new “extension alone forces access control” path. A regression there could slip by whileisAccessControlRequired()stays green. I’d add at least one{ contentUri: true, upgradeable: false }and one{ metadata: true, upgradeable: false }case in bothwith_components_onandwith_components_off.🧪 Minimal additions
testERC6909('metadata', { metadata: true, }); +testERC6909('content uri non-upgradeable', { + contentUri: true, + upgradeable: false, +}); + +testERC6909('metadata non-upgradeable', { + metadata: true, + upgradeable: false, +}); + testERC6909('token supply + pausable', { tokenSupply: true, pausable: true,Based on learnings: In the OpenZeppelin contracts-wizard cairo_alpha package, when the
uriStorageoption is enabled for ERC1155 (or ERC721), access control is required. Ifaccess: AccessControl.None()is specified along withuriStorage: true, the contract builder automatically switches to the default access control (Ownable) to ensure URI storage functions (likeset_base_uriandset_token_uri) are protected. This is intentional behavior to maintain security.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts` around lines 63 - 89, The test matrix is missing non-upgradeable cases that exercise the "extension alone forces access control" path; add at least one testERC6909 invocation for { contentUri: true, upgradeable: false } and one for { metadata: true, upgradeable: false } in both the with_components_on and with_components_off test files so the builder's automatic default access control behavior is covered; locate the existing testERC6909 calls and duplicate them with the new option objects (preserving the same test name pattern) and run/update assertions if any rely on upgradeable behavior.packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md (1)
420-427: Consider normalizing constructor argument ordering across extension combinations.
owner/role addresses and metadata fields are ordered differently between variants (for example, metadata-only vs content-uri+metadata/all-extensions). Keeping a stable ordering convention will reduce deployment-script churn when toggling options.Also applies to: 580-587, 674-681, 1023-1034, 1173-1184, 1337-1348, 1485-1496, 1643-1654, 1809-1820
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md` around lines 420 - 427, The constructors across ERC6909 test variants have inconsistent argument ordering (e.g., token_id, token_name, token_symbol, token_decimals, owner vs other orders); standardize the parameter order for every `constructor` definition so deployment scripts don’t need per-variant changes—pick a canonical ordering (suggest: token_id, token_name, token_symbol, token_decimals, owner) and update all `constructor` declarations and any corresponding calls/usages in the metadata-only, content-uri+metadata, and all-extensions variants (including the instances noted around the ranges provided) to match that canonical order.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/core/cairo_alpha/src/erc6909.ts`:
- Around line 84-92: Add a changelog entry to
packages/core/cairo_alpha/CHANGELOG.md under the Unreleased section documenting
the ERC6909 surface changes (e.g., addition of contentUri, tokenSupply, metadata
options reflected by addContentURI, addTokenSupply, addMetadata in erc6909.ts);
include a short summary of the change, the affected files
(packages/core/cairo_alpha/src/erc6909.ts), and the PR/author reference so
consumers can see the new generated surface and why the package version needs
updating.
In `@packages/ui/src/cairo_alpha/ERC6909Controls.svelte`:
- Around line 58-67: The tooltips for the Content URI and Supply Tracking
options reference hardcoded camelCase method names that don't match generated
Cairo snake_case APIs; update the <HelpTooltip> text used inside the label
elements for opts.contentUri and opts.tokenSupply to remove specific method
signatures (e.g., remove "contractURI()", "tokenURI(id)", "totalSupply(id)") and
replace with generic descriptions like "Provides contract-level and per-token
URI metadata" and "Tracks total supply per token ID" so the text doesn't point
to camelCase names.
---
Nitpick comments:
In
`@packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts`:
- Around line 63-89: The test matrix is missing non-upgradeable cases that
exercise the "extension alone forces access control" path; add at least one
testERC6909 invocation for { contentUri: true, upgradeable: false } and one for
{ metadata: true, upgradeable: false } in both the with_components_on and
with_components_off test files so the builder's automatic default access control
behavior is covered; locate the existing testERC6909 calls and duplicate them
with the new option objects (preserving the same test name pattern) and
run/update assertions if any rely on upgradeable behavior.
In
`@packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md`:
- Around line 420-427: The constructors across ERC6909 test variants have
inconsistent argument ordering (e.g., token_id, token_name, token_symbol,
token_decimals, owner vs other orders); standardize the parameter order for
every `constructor` definition so deployment scripts don’t need per-variant
changes—pick a canonical ordering (suggest: token_id, token_name, token_symbol,
token_decimals, owner) and update all `constructor` declarations and any
corresponding calls/usages in the metadata-only, content-uri+metadata, and
all-extensions variants (including the instances noted around the ranges
provided) to match that canonical order.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 20030574-a299-4d30-8cb7-4f9984ab08f7
⛔ Files ignored due to path filters (2)
packages/core/cairo_alpha/src/tests/with_components_off/erc6909/erc6909.test.ts.snapis excluded by!**/*.snappackages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.snapis excluded by!**/*.snap
📒 Files selected for processing (9)
packages/common/src/ai/descriptions/cairo.tspackages/core/cairo_alpha/src/erc6909.tspackages/core/cairo_alpha/src/generate/erc6909.tspackages/core/cairo_alpha/src/tests/with_components_off/erc6909/erc6909.test.tspackages/core/cairo_alpha/src/tests/with_components_off/erc6909/erc6909.test.ts.mdpackages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.tspackages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.mdpackages/ui/api/ai-assistant/function-definitions/cairo-alpha.tspackages/ui/src/cairo_alpha/ERC6909Controls.svelte
| if (allOpts.contentUri) { | ||
| addContentURI(c, allOpts.access); | ||
| } | ||
| if (allOpts.tokenSupply) { | ||
| addTokenSupply(c); | ||
| } | ||
| if (allOpts.metadata) { | ||
| addMetadata(c, allOpts.access); | ||
| } |
There was a problem hiding this comment.
Please add the matching cairo_alpha changelog entry.
This PR changes the generated ERC6909 surface under packages/core/cairo_alpha, but the patch doesn’t include the corresponding packages/core/cairo_alpha/CHANGELOG.md update.
Based on learnings: Changes within packages/core/cairo_alpha should have a corresponding changelog entry in packages/core/cairo_alpha/CHANGELOG.md under the Unreleased section to track these changes.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/core/cairo_alpha/src/erc6909.ts` around lines 84 - 92, Add a
changelog entry to packages/core/cairo_alpha/CHANGELOG.md under the Unreleased
section documenting the ERC6909 surface changes (e.g., addition of contentUri,
tokenSupply, metadata options reflected by addContentURI, addTokenSupply,
addMetadata in erc6909.ts); include a short summary of the change, the affected
files (packages/core/cairo_alpha/src/erc6909.ts), and the PR/author reference so
consumers can see the new generated surface and why the package version needs
updating.
| <label class:checked={opts.contentUri}> | ||
| <input type="checkbox" bind:checked={opts.contentUri} /> | ||
| Content URI | ||
| <HelpTooltip>Provides contract-level and per-token URI metadata via contractURI() and tokenURI(id).</HelpTooltip> | ||
| </label> | ||
| <label class:checked={opts.tokenSupply}> | ||
| <input type="checkbox" bind:checked={opts.tokenSupply} /> | ||
| Supply Tracking | ||
| <HelpTooltip>Keeps track of total supply per token ID via totalSupply(id).</HelpTooltip> | ||
| </label> |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
In OpenZeppelin Contracts for Cairo alpha ERC-6909 Content URI and Token Supply extensions, what are the exposed read method names? Are they snake_case (contract_uri, token_uri, total_supply) or camelCase wrappers (contractURI, tokenURI, totalSupply)?
💡 Result:
In OpenZeppelin Contracts for Cairo (alpha), the ERC token components typically expose both:
- the snake_case Cairo-style external methods, and
- camelCase wrappers (for Solidity-/EVM-style naming / legacy tooling expectations).
This is visible in the Cairo alpha API docs for ERC-721, where both token_uri(...) and tokenURI(...) are exposed as external methods. (docs.openzeppelin.com)
So for ERC-6909 extensions you should expect the exposed read methods to include both name variants:
- Content URI extension
contract_uri()andcontractURI()token_uri(id)andtokenURI(id)
- Token Supply extension
total_supply(id)andtotalSupply(id)
Citations:
🏁 Script executed:
# Search for ERC-6909 implementation and Content URI / Token Supply extensions
find . -type f -name "*.ts" -o -name "*.cairo" | xargs grep -l "ERC6909\|contentUri\|tokenSupply" 2>/dev/null | head -20Repository: OpenZeppelin/contracts-wizard
Length of output: 1138
🏁 Script executed:
# Look for test snapshots or generated code that shows the actual Cairo API surface
fd -e "test.ts.md" -e ".test.ts" | xargs grep -l "ERC6909\|contract_uri\|token_uri\|totalSupply" 2>/dev/null | head -10Repository: OpenZeppelin/contracts-wizard
Length of output: 816
🏁 Script executed:
# Check the test snapshot for ERC6909 with components ON to see generated method names
wc -l ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.mdRepository: OpenZeppelin/contracts-wizard
Length of output: 161
🏁 Script executed:
# Search for contentUri and tokenSupply related code in the test snapshot
rg "contentUri|tokenSupply" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md -A 5 -B 2Repository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Look for the actual Cairo method signatures in the test snapshot - search for contract_uri, token_uri, total_supply
rg "contract_uri|token_uri|total_supply|contractURI|tokenURI|totalSupply" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md | head -30Repository: OpenZeppelin/contracts-wizard
Length of output: 2471
🏁 Script executed:
# Search for the getter/read methods (without set_ prefix) for contract_uri and token_uri
rg "fn contract_uri|fn token_uri|fn total_supply" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md -A 2 | head -40Repository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Look at a specific section of the test file to see the full generated contract with all methods
sed -n '1,200p' ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md | grep -A 3 "fn contract_uri\|fn token_uri\|fn total_supply"Repository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Search for the generated contract code more broadly to see all exposed methods
rg "pub fn contract_uri|pub fn token_uri|pub fn total_supply|pub fn contractURI|pub fn tokenURI|pub fn totalSupply" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.mdRepository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Let's look at the actual ERC6909 generation code to understand what methods are created
cat ./packages/core/cairo_alpha/src/generate/erc6909.tsRepository: OpenZeppelin/contracts-wizard
Length of output: 1356
🏁 Script executed:
# Also check the contentUri component implementation
fd -type f -name "*content*uri*" -o -name "*ContentUri*"Repository: OpenZeppelin/contracts-wizard
Length of output: 243
🏁 Script executed:
# Search for where the read methods are defined in the component source
rg "contract_uri|token_uri|total_supply" ./packages/core/cairo_alpha/src -t ts -l | head -10Repository: OpenZeppelin/contracts-wizard
Length of output: 200
🏁 Script executed:
# Check the erc6909.ts file to see the options interface
cat ./packages/core/cairo_alpha/src/erc6909.tsRepository: OpenZeppelin/contracts-wizard
Length of output: 10420
🏁 Script executed:
# Look for the actual component implementations or built templates
fd -name "*.cairo" -path "*6909*" 2>/dev/nullRepository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Search in the test snapshot for where read methods are called or defined
rg "fn contract_uri|fn token_uri|fn total_supply|contract_uri\(\)|token_uri\(" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md -B 2 -A 3 | head -50Repository: OpenZeppelin/contracts-wizard
Length of output: 1868
🏁 Script executed:
# Search for the getter methods in the test snapshot - look for all methods with contract_uri or token_uri in the name
rg "fn.*contract_uri|fn.*token_uri|fn.*total_supply" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md -B 1 -A 3 | head -60Repository: OpenZeppelin/contracts-wizard
Length of output: 2736
🏁 Script executed:
# Alternative: search for the implementation trait methods that would be exposed
rg "ERC6909ContentURIImpl|ERC6909TokenSupplyImpl" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md -B 3 -A 10 | head -80Repository: OpenZeppelin/contracts-wizard
Length of output: 3170
🏁 Script executed:
# Check if there's any documentation or component definition that lists the available methods
rg "contract_uri|token_uri|total_supply" ./packages/core/cairo_alpha/src -g "*.ts" -B 2 -A 2 | grep -A 3 "ERC6909ContentURI\|ERC6909TokenSupply" | head -50Repository: OpenZeppelin/contracts-wizard
Length of output: 522
🏁 Script executed:
# Search for calls to contract_uri, token_uri, total_supply in the test (as reads/getters)
rg "contract_uri\(|token_uri\(|total_supply\(|contractURI\(|tokenURI\(|totalSupply\(" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.mdRepository: OpenZeppelin/contracts-wizard
Length of output: 2952
🏁 Script executed:
# Look for the actual impl block contents to see what public methods are exposed
sed -n '1,500p' ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md | tail -200Repository: OpenZeppelin/contracts-wizard
Length of output: 7048
🏁 Script executed:
# Check if there are any test calls or assertions that invoke the read methods
rg "\.contract_uri\(|\.token_uri\(|\.total_supply\(" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.mdRepository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Search for how other Cairo components expose read methods to understand the pattern
rg "fn contract_uri|fn token_uri|fn total_supply" ./packages/core/cairo_alpha/src -B 2 -A 5Repository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Check the OpenZeppelin Contracts for Cairo documentation links in the generated code
rg "Compatible with OpenZeppelin Contracts for Cairo" ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.mdRepository: OpenZeppelin/contracts-wizard
Length of output: 1492
🏁 Script executed:
# Look at what's embedded in the trait/impl for the ContentURI component specifically
sed -n '1,100p' ./packages/core/cairo_alpha/src/tests/with_components_on/erc6909/erc6909.test.ts.md | grep -A 20 "ERC6909ContentURIImpl"Repository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Look at the ERC1155 test to see if we can find a pattern for how URI read methods are named
rg "contract_uri\(|token_uri\(" ./packages/core/cairo_alpha/src/tests/with_components_on/erc1155/erc1155.test.ts.md | head -20Repository: OpenZeppelin/contracts-wizard
Length of output: 1802
🏁 Script executed:
# Check what methods the ERC1155URIStorageComponent actually exposes by looking for any calls to it
rg "erc1155_uri_storage\." ./packages/core/cairo_alpha/src/tests/with_components_on/erc1155/erc1155.test.ts.md -A 2 | head -40Repository: OpenZeppelin/contracts-wizard
Length of output: 1057
🏁 Script executed:
# Search in the UI file itself to see if there are any other references to these methods
grep -r "contractURI\|tokenURI\|totalSupply" ./packages/ui/src/cairo_alpha/ 2>/dev/nullRepository: OpenZeppelin/contracts-wizard
Length of output: 393
🏁 Script executed:
# Let's look for any getter method definitions in the ERC6909 component by checking what's embedded
rg "ERC6909ContentURIImpl|ERC6909TokenSupplyImpl" ./packages/core/cairo_alpha/src -B 3 -A 10 -g "*.ts" | head -100Repository: OpenZeppelin/contracts-wizard
Length of output: 2329
🏁 Script executed:
# Check if there's a definition of what methods these components expose
find ./packages/core/cairo_alpha/src -name "*.ts" -exec grep -l "ERC6909ContentURI\|ERC6909TokenSupply" {} \;Repository: OpenZeppelin/contracts-wizard
Length of output: 115
🏁 Script executed:
# Search in the broader OpenZeppelin Cairo package context to understand if ERC6909 is documented
find ./packages -name "CHANGELOG.md" -o -name "README.md" | xargs grep -l "ERC6909\|6909" 2>/dev/nullRepository: OpenZeppelin/contracts-wizard
Length of output: 184
🏁 Script executed:
# Check if the web search claim about both variants is validated by looking at an ERC721 example in the tests
rg "fn token_uri|fn tokenURI" ./packages/core/cairo_alpha/src/tests/with_components_on/erc721/erc721.test.ts.md | head -20Repository: OpenZeppelin/contracts-wizard
Length of output: 55
🏁 Script executed:
# Look for any documentation in the wizard about which methods are actually exposed
rg "contractURI|tokenURI|totalSupply|contract_uri|token_uri|total_supply" ./packages/ui/src/cairo_alpha -B 3 -A 3Repository: OpenZeppelin/contracts-wizard
Length of output: 1308
🏁 Script executed:
# Check the changelog to see if ERC6909 components are mentioned as new
grep -A 5 -B 5 "ERC6909\|6909" ./packages/core/cairo_alpha/CHANGELOG.md | head -50Repository: OpenZeppelin/contracts-wizard
Length of output: 997
🏁 Script executed:
# Final verification: look for any test that actually calls these read methods to confirm they exist
rg "\.contract_uri\(\)|\.token_uri\(\)|\.total_supply\(\)|contractURI\(\)|tokenURI\(\)|totalSupply\(\)" ./packages/core/cairo_alpha/src/tests -B 2 -A 2Repository: OpenZeppelin/contracts-wizard
Length of output: 55
Remove hardcoded camelCase method names from these tooltips.
The generated Cairo code exposes snake_case methods for URI setters and does not include camelCase wrappers (new features skip backwards-compat naming). The tooltips should omit specific method signatures to avoid pointing users at names that don't match the generated API:
✏️ Suggested rewording
- <HelpTooltip>Provides contract-level and per-token URI metadata via contractURI() and tokenURI(id).</HelpTooltip>
+ <HelpTooltip>Provides contract-level and per-token URI metadata.</HelpTooltip>
...
- <HelpTooltip>Keeps track of total supply per token ID via totalSupply(id).</HelpTooltip>
+ <HelpTooltip>Keeps track of total supply per token ID.</HelpTooltip>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <label class:checked={opts.contentUri}> | |
| <input type="checkbox" bind:checked={opts.contentUri} /> | |
| Content URI | |
| <HelpTooltip>Provides contract-level and per-token URI metadata via contractURI() and tokenURI(id).</HelpTooltip> | |
| </label> | |
| <label class:checked={opts.tokenSupply}> | |
| <input type="checkbox" bind:checked={opts.tokenSupply} /> | |
| Supply Tracking | |
| <HelpTooltip>Keeps track of total supply per token ID via totalSupply(id).</HelpTooltip> | |
| </label> | |
| <label class:checked={opts.contentUri}> | |
| <input type="checkbox" bind:checked={opts.contentUri} /> | |
| Content URI | |
| <HelpTooltip>Provides contract-level and per-token URI metadata.</HelpTooltip> | |
| </label> | |
| <label class:checked={opts.tokenSupply}> | |
| <input type="checkbox" bind:checked={opts.tokenSupply} /> | |
| Supply Tracking | |
| <HelpTooltip>Keeps track of total supply per token ID.</HelpTooltip> | |
| </label> |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/ui/src/cairo_alpha/ERC6909Controls.svelte` around lines 58 - 67, The
tooltips for the Content URI and Supply Tracking options reference hardcoded
camelCase method names that don't match generated Cairo snake_case APIs; update
the <HelpTooltip> text used inside the label elements for opts.contentUri and
opts.tokenSupply to remove specific method signatures (e.g., remove
"contractURI()", "tokenURI(id)", "totalSupply(id)") and replace with generic
descriptions like "Provides contract-level and per-token URI metadata" and
"Tracks total supply per token ID" so the text doesn't point to camelCase names.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
| - Add ERC6909Metadata extension ([#793](https://github.com/OpenZeppelin/contracts-wizard/pull/793)) | ||
| - Add ERC6909ContentURI extension ([#793](https://github.com/OpenZeppelin/contracts-wizard/pull/793)) | ||
| - Add ERC6909TokenSupply extension ([#793](https://github.com/OpenZeppelin/contracts-wizard/pull/793)) |
There was a problem hiding this comment.
| - Add ERC6909Metadata extension ([#793](https://github.com/OpenZeppelin/contracts-wizard/pull/793)) | |
| - Add ERC6909ContentURI extension ([#793](https://github.com/OpenZeppelin/contracts-wizard/pull/793)) | |
| - Add ERC6909TokenSupply extension ([#793](https://github.com/OpenZeppelin/contracts-wizard/pull/793)) | |
| Cairo: Add ERC6909Metadata, ERC6909ContentURI, ERC6909TokenSupply extensions |
| <label class:checked={opts.contentUri}> | ||
| <input type="checkbox" bind:checked={opts.contentUri} /> | ||
| Content URI | ||
| <HelpTooltip>Provides contract-level and per-token URI metadata via contract_uri() and token_uri(id).</HelpTooltip |
There was a problem hiding this comment.
Is there any documentation that we can link to using link= which describes the exposed functions/behavior, instead of directly listing the functions here? Same for the other new fields below. The function names are fine but may be hard to read in this format.
If we do want to list the exposed function names, we could use <code>...</code> to format them.
There was a problem hiding this comment.
We didnt create a docsite version for the latest alpha, so there is no matching doc ref. That's on us and something we need to be paying attention to, cc @immrsd and @bidzyyys. Since we are still releasing alphas, we should continue releasing doc-site versions for them. It is sadly somewhat harder to keep up-to-date now that the doc contents are in a different repo...
4 participants
Resolves #1591
Adds support for the three
ERC-6909component's extensions: