Bridging Standard ERC-20 tutorial update

[krofax]

Description

Update the links to OptimismMintableERC20Factory.

Tests

Additional context

Metadata

• Fixes : https://github.com/ethereum-optimism/devrel/issues/567

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	58c5265
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67e1907cef47f80007e4f25e
😎 Deploy Preview	https://deploy-preview-1528--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request removes the WipCallout component and its associated markup from the bridging tutorial at pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx. It also updates the reference to the IOptimismMintableERC20 interface by changing the link from version v1.1.4 to v1.12.0 in the document. The update points to the new OptimismMintableERC20.sol file, ensuring that the documentation reflects the current version of the interface while maintaining the overall guidance on bridging ERC-20 tokens via the Standard Bridge.

Possibly related PRs

• Fix old link found on "Bridging Your Standard ERC-20 Token Using the Standard Bridge" tutorial page #1023: This PR also updated the interface reference link for IOptimismMintableERC20, aligning closely with the changes introduced in this pull request.

Suggested reviewers

• zainbacchus
• bradleycamacho

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 65991f9 and 58c5265.

📒 Files selected for processing (1)

• pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with the following criteria: - First, check the frontmatter section at the top of the file: 1. For regular pages, ensure AL...

**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

• First, check the frontmatter section at the top of the file:
  1. For regular pages, ensure ALL these fields are present and not empty:

  ---
  title: [non-empty]
  lang: [non-empty]
  description: [non-empty]
  topic: [non-empty]
  personas: [non-empty array]
  categories: [non-empty array]
  content_type: [valid type]
  ---

  2. For landing pages (index.mdx or files with ), only these fields are required:

  ---
  title: [non-empty]
  lang: [non-empty]
  description: [non-empty]
  topic: [non-empty]
  ---

  3. If any required fields are missing or empty, comment:
     'This file appears to be missing required metadata. You can fix this by running:

  pnpm metadata-batch-cli:dry "path/to/this/file.mdx"

  Review the changes, then run without :dry to apply them.'
• Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
• Avoid gender-specific language and use the imperative form.
• Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
• Ensure proper nouns are capitalized in sentences.
• Apply the Oxford comma.
• Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
• Use correct spelling and grammar at all times (IMPORTANT).
• For H1, H2, and H3 headers:
  1. Use sentence case, capitalizing only the first word.
  2. Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
  3. Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
• Flag any headers that seem to inconsistently apply these rules for manual review.
• When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
  "

• pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism

🔇 Additional comments (3)

pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx (3)

1-16: Frontmatter metadata is comprehensive and correctly formatted
All required frontmatter fields (title, description, lang, content_type, topic, personas, categories, and is_imported_content) are present and appear valid.

---

35-38: Updated interface reference link to version v1.12.0
The link for the IOptimismMintableERC20 interface has been updated to reflect version v1.12.0. This update ensures the documentation now points to the current implementation of the interface. Please verify that any downstream references or contract integrations are compatible with this version change.

🧰 Tools

🪛 LanguageTool

[style] ~37-~37: Consider a shorter alternative to avoid wordiness.
Context: ... contract must implement this interface in order to be bridged using the Standard Bridge sy...

(IN_ORDER_TO_PREMIUM)

---

29-31: Removal of the WipCallout component
According to the PR objectives, the WipCallout component and its associated markup have been removed. Verify that no other parts of the documentation or related tutorial pages reference or depend on the removed component.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.