Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(input-otp): autofocus #4296

Merged
merged 2 commits into from
Dec 9, 2024
Merged

fix(input-otp): autofocus #4296

merged 2 commits into from
Dec 9, 2024

Conversation

macci001
Copy link
Contributor

@macci001 macci001 commented Dec 9, 2024

Closes #4250

📝 Description

Fixes the autofocus functionality in input-otp component## ⛳️ Current behavior (updates)

Current behavior

Screen.Recording.2024-12-09.at.7.32.24.PM.mov

🚀 New behavior

Screen.Recording.2024-12-09.at.7.34.02.PM.mov

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

  • New Features

    • Introduced autofocus functionality for the OTP input component, improving user experience.
  • Bug Fixes

    • Resolved issues related to the autofocus behavior of the OTP input component.
  • Tests

    • Added new test cases to verify the autofocus feature for the OTP input component.
  • Documentation

    • Updated documentation to include the new autoFocus property for the OTP input component.

@macci001 macci001 requested a review from jrgarciadev as a code owner December 9, 2024 14:05
Copy link

changeset-bot bot commented Dec 9, 2024

🦋 Changeset detected

Latest commit: 780d88a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@nextui-org/input-otp Patch
@nextui-org/react Patch

Not sure what this means? Click here to learn what changesets are.

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

Copy link

vercel bot commented Dec 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 9, 2024 3:37pm
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 9, 2024 3:37pm

Copy link
Contributor

coderabbitai bot commented Dec 9, 2024

Walkthrough

This pull request introduces a patch to the @nextui-org/input-otp component to fix the autofocus functionality. The changes include adding an autoFocus property to the getInputOtpProps function in the useInputOtp hook, enabling the component to focus on the first input segment when rendered. Additionally, new test cases have been added to verify the autofocus behavior under different conditions.

Changes

File Change Summary
.changeset/smooth-trainers-walk.md Patch for @nextui-org/input-otp to fix autofocus functionality.
packages/components/input-otp/__tests__/input-otp.test.tsx Added tests for autofocus behavior when the autoFocus prop is passed or omitted.
packages/components/input-otp/src/use-input-otp.ts Added autoFocus property to getInputOtpProps function and adjusted logic in useInputOtp.
apps/docs/content/docs/components/input-otp.mdx Updated documentation to include autoFocus property in InputOtp Props.

Assessment against linked issues

Objective Addressed Explanation
Autofocus should work when autoFocus prop is set (#4250)

Possibly related PRs

Suggested labels

👀 Status: In Review

Suggested reviewers

  • wingkwong
  • jrgarciadev

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
packages/components/input-otp/src/use-input-otp.ts (1)

Line range hint 233-246: Add autoFocus to the dependencies array of useCallback.

The autoFocus prop is used in getInputOtpProps but isn't included in its dependencies array, which could lead to stale closures.

Update the dependencies array to include autoFocus:

    [
      isRequired,
      isDisabled,
      isReadOnly,
      allowedKeys,
      inputRef,
      name,
      value,
      length,
      setValue,
      props.onBlur,
      onComplete,
+     originalProps.autoFocus,
    ],
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3d782a2 and 1def199.

📒 Files selected for processing (3)
  • .changeset/smooth-trainers-walk.md (1 hunks)
  • packages/components/input-otp/__tests__/input-otp.test.tsx (1 hunks)
  • packages/components/input-otp/src/use-input-otp.ts (1 hunks)
🔇 Additional comments (3)
.changeset/smooth-trainers-walk.md (1)

1-5: LGTM! Changeset correctly describes the patch.

The changeset properly identifies this as a patch update and references the correct issue (#4250).

packages/components/input-otp/__tests__/input-otp.test.tsx (1)

172-185: LGTM! Test coverage is comprehensive.

The new test cases effectively verify both:

  1. Autofocus behavior when the prop is passed
  2. Default behavior when the prop is not passed

The assertions are correct and follow the established patterns in the test suite.

packages/components/input-otp/src/use-input-otp.ts (1)

233-233: LGTM! Implementation correctly handles autoFocus.

The autoFocus prop is properly forwarded to the underlying input component and integrates well with the existing focus management system.

@wingkwong wingkwong changed the title fix: autofocus the input-otp when auto-focus prop is passed fix(input-otp): autofocus Dec 9, 2024
@wingkwong wingkwong added this to the v2.6.6 milestone Dec 9, 2024
Copy link
Member

@wingkwong wingkwong left a comment

Choose a reason for hiding this comment

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
apps/docs/content/docs/components/input-otp.mdx (2)

306-311: Enhance the autoFocus prop documentation

While the basic documentation is correct, consider expanding the description to provide more context and usage guidance:

     {
       attribute: "autoFocus",
       type: "boolean",
-      description: "Whether the element should receive focus on render.",
+      description: "When true, the first input segment automatically receives focus when the component mounts. Useful in multi-step forms or after navigation.",
       default: "false"
     },

Line range hint 1-500: Consider adding autoFocus examples and accessibility notes

To provide comprehensive documentation for the new autoFocus feature, consider:

  1. Adding an example in the Usage section demonstrating the autoFocus prop
  2. Including a note in the Accessibility section about the autofocus behavior and its implications for screen readers

Would you like me to help draft these additional documentation sections?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between fffa4bb and 780d88a.

📒 Files selected for processing (3)
  • apps/docs/content/docs/components/input-otp.mdx (1 hunks)
  • packages/components/input-otp/__tests__/input-otp.test.tsx (1 hunks)
  • packages/components/input-otp/src/use-input-otp.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/components/input-otp/tests/input-otp.test.tsx
  • packages/components/input-otp/src/use-input-otp.ts

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.

[BUG] - OTP Autofocus doesn't work
2 participants