updated otp input

[ankitmlesmagico]

Summary by CodeRabbit

• New Features

  • Improved OTP input field with enhanced key event handling and styling.

• Chores

  • Updated versions for multiple packages to ensure compatibility and stability across the application.

[vercel]

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

Name	Status	Preview	Updated (UTC)
stencil-ui	❌ Failed (Inspect)		Jul 11, 2024 11:51am

[coderabbitai]

Walkthrough

This update primarily involves version increments across various packages, namely chatui, config-manager, hooks, molecules, and provider. Additionally, there are minor adjustments in dependency references and some restructuring within the molecules package, specifically updating import paths and the logic within the OTPInput component to align with the new dependencies.

Changes

File/Directory	Change Summary
packages/chatui/package.json	Updated the version from "0.0.1" to "0.0.7".
packages/config-manager/package.json	Updated the version from "0.0.1" to "0.0.7".
packages/hooks/package.json	Updated the version from "0.0.1" to "0.0.8". Updated dependency on @samagra-x/stencil-provider from "0.0.1" to "0.0.7".
packages/molecules/package.json	Updated the version from "0.0.1" to "0.0.11". Modified "main", added "module", "browser", "style", and "typings" entries. Updated dependencies.
packages/molecules/src/otp-input/index.tsx	Changed import statements from @mui/material to @mui/system and @mui/base/Input. Modified logic for key events handling and styling.
packages/provider/package.json	Updated the version from "0.0.1" to "0.0.7". Updated dependency on @samagra-x/stencil-config-manager from "0.0.1" to "0.0.7".

Poem

In the land of code and byte,
Versions leap from night to light.
Smooth transitions, imports align,
OTPInput now divine.
Dependencies dance in harmony,
Chatbots hum a sweet melody.
🐰✨ CodeRabbit smiles, all is right.

---

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

• 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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ff815df and 5d6bc1a.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (6)

• packages/chatui/package.json (1 hunks)
• packages/config-manager/package.json (1 hunks)
• packages/hooks/package.json (2 hunks)
• packages/molecules/package.json (2 hunks)
• packages/molecules/src/otp-input/index.tsx (7 hunks)
• packages/provider/package.json (2 hunks)

Files skipped from review due to trivial changes (5)

• packages/chatui/package.json
• packages/config-manager/package.json
• packages/hooks/package.json
• packages/molecules/package.json
• packages/provider/package.json

Additional comments not posted (4)

packages/molecules/src/otp-input/index.tsx (4)

Line range hint 28-74:
LGTM! Key event handling changes are correct.

The key event handling changes for ArrowUp, ArrowDown, , ArrowLeft, ArrowRight, Delete, and Backspace keys are correctly implemented. Ensure that these changes are tested thoroughly.

---

Line range hint 75-133:
LGTM! Input processing changes are correct.

The input processing changes for handling change, click, and paste events are correctly implemented. Ensure that these changes are tested thoroughly.

---

Line range hint 135-217:
LGTM! Styling adjustments are correct.

The styling adjustments to the Box component and InputElement are correctly implemented. Ensure that these changes are tested thoroughly.

---

1-3: LGTM! But verify the updated imports.

The import statements have been updated to use @mui/system and @mui/base/Input instead of @mui/material. Ensure that these changes are intentional and that the functionality remains intact.