Skip to content

Clean up builder codes UI#5

Closed
yosriady wants to merge 1 commit intomainfrom
chore/rm-builder-codes
Closed

Clean up builder codes UI#5
yosriady wants to merge 1 commit intomainfrom
chore/rm-builder-codes

Conversation

@yosriady
Copy link
Contributor

@yosriady yosriady commented Mar 6, 2026

@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@yosriady yosriady closed this Mar 6, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the application by eliminating the 'builder code' functionality and its corresponding UI. The changes focus on removing unused components, state, and dependencies that were previously involved in handling ERC-8021 builder codes, resulting in a cleaner and more focused codebase.

Highlights

  • Removed Builder Code UI: The user interface elements related to 'builder codes' have been completely removed from the WriteOnlyFunctionForm component, including the input field and associated state management.
  • Removed SendTransaction Component: The dedicated SendTransaction component, which previously handled sending test transactions with builder codes, has been deleted from the project.
  • Dependency Cleanup: The ox dependency, which was used for Attribution related to ERC-8021 builder codes, has been removed from package.json.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • with-next-app-router/packages/nextjs/app/debug/_components/contract/WriteOnlyFunctionForm.tsx
    • Removed the import for Attribution from ox/erc8021.
    • Deleted the builderCode state variable and its setter.
    • Removed the conditional logic that added dataSuffix based on builderCode to transaction parameters.
    • Updated the zeroInputs calculation to correctly reflect the presence of inputs.
    • Removed the entire UI block for the 'builder code' input field.
  • with-next-app-router/packages/nextjs/app/page.tsx
    • Removed the import statement for the SendTransaction component.
    • Deleted the JSX rendering of the SendTransaction component from the main page.
  • with-next-app-router/packages/nextjs/components/SendTransaction.tsx
    • The SendTransaction.tsx file, containing the SendTransaction component, was entirely removed.
  • with-next-app-router/packages/nextjs/package.json
    • Removed the ox package from the list of dependencies.
Activity
  • The pull request was opened with a title indicating a cleanup of builder codes UI.
  • No additional comments or reviews have been posted yet, aside from an automated Devin review badge.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request effectively cleans up the UI by removing the 'builder code' functionality. The changes are well-executed, including the removal of the SendTransaction component, the associated ox dependency, and all related logic and UI elements from WriteOnlyFunctionForm. The update to the zeroInputs logic is a good correction following the removal of the builder code input. The codebase is now cleaner and more focused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant