Skip to content

doca: Update iq-login setup in next app#143

Merged
Adebesin-Cell merged 1 commit intomainfrom
docs/update-readme
Feb 3, 2026
Merged

doca: Update iq-login setup in next app#143
Adebesin-Cell merged 1 commit intomainfrom
docs/update-readme

Conversation

@Adebesin-Cell
Copy link
Copy Markdown
Member

@Adebesin-Cell Adebesin-Cell commented Feb 3, 2026

No description provided.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 3, 2026

⚠️ No Changeset found

Latest commit: 4c370f2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @Adebesin-Cell, 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 refactors the integration of the iq-login library within Next.js applications by updating the configuration method. It transitions from using getWagmiConfig to createIqLoginConfig and adjusts the IqLoginProvider component to accept the new config prop, streamlining the setup process for supported chains and ensuring the documentation matches the new implementation.

Highlights

  • Configuration Update: The iq-login setup in Next.js applications has been updated to use createIqLoginConfig instead of getWagmiConfig for generating the login configuration.
  • Provider Prop Change: The IqLoginProvider component now accepts a config prop instead of wagmiConfig, streamlining the configuration passing.
  • Documentation Alignment: The README.md file has been updated to reflect these changes, ensuring the setup instructions are current and accurate.

🧠 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
  • README.md
    • Updated import statement to include createIqLoginConfig from @everipedia/iq-login/client.
    • Replaced getWagmiConfig with createIqLoginConfig for initializing the login configuration.
    • Modified IqLoginProvider to use the config prop instead of wagmiConfig.
    • Removed the commented-out chains prop from the IqLoginProvider example, as chain configuration is now handled by createIqLoginConfig.
    • Updated instructional text to guide users to pass chains to createIqLoginConfig.
Activity
  • The pull request was created by Adebesin-Cell.
  • The changes primarily involve updating the iq-login integration instructions and code examples in README.md.
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.

@Adebesin-Cell Adebesin-Cell merged commit 6b9010f into main Feb 3, 2026
1 check passed
@Adebesin-Cell Adebesin-Cell deleted the docs/update-readme branch February 3, 2026 18:27
Copy link
Copy Markdown

@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 updates the documentation in README.md to reflect recent API changes in the iq-login package, specifically replacing getWagmiConfig with createIqLoginConfig. The changes are clear and correctly guide the user on the new setup process. I've added one suggestion to improve the clarity of the code example by documenting the default chain behavior.

Comment thread README.md
// Get the Wagmi config. It is important that this is outside the component
const wagmiConfig = getWagmiConfig([fraxtal])
// Create the config. It is important that this is outside the component
const config = createIqLoginConfig([fraxtal])
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve clarity for developers using this package, it would be beneficial to add a comment indicating that createIqLoginConfig defaults to mainnet if no chains are provided. This helps users understand the default behavior without needing to check the source code.

Suggested change
const config = createIqLoginConfig([fraxtal])
const config = createIqLoginConfig([fraxtal]) // Defaults to [mainnet] if no chains are provided

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