refactor: ion input with styled components

[danilo-moreira-brisa]

Summary by CodeRabbit

• New Features
  • Introduced a new focus feature for the IonInput component, enhancing usability by focusing on the input when its container is clicked.
  • Added theme-based styling support for input components, allowing for more consistent and customizable designs.
• Refactor
  • Refactored input component styles for better maintainability and readability.
  • Improved testing setup for the IonInput component for more robust testing outcomes.
• Enhancements
  • Updated the Password component to disable autocomplete, enhancing security and user privacy.
  • Extended theme utility functions to include a start function for more flexible item alignment in flex layouts.

[coderabbitai]

Walkthrough

The recent update involves a significant refactor of the IonInput component, incorporating styled-components for enhanced styling flexibility and theme integration. It also introduces a new focus management feature via a ref and optimizes the component's compatibility with additional props. The styling overhaul extends to the component's styles, ensuring consistency and theme adherence. Testing and storybook enhancements accompany these changes for better development experience and documentation.

Changes

Files	Change Summary
src/components/input/input.tsx	Updated to use styled-components, added ref for focus.
src/components/input/styles.ts	Refactored with styled-components, theme-based styling.
src/components/input/input.test.tsx	Adjusted tests to use renderWithTheme.
src/stories/input/input.stories.tsx	Improved storybook with autoComplete: 'off' for Password.
src/styles/theme.ts	Added start function in utils.flex for alignment.

Possibly related issues

• refactor: ion input #131: Refactors IonInput to use styled-components, directly aligning with the PR's objectives.
• refactor: ion button #123: Although focused on IonButton, it shares the goal of adopting styled-components, hinting at a broader refactoring strategy this PR is part of.

🐇✨
In a field of code, under a sky so wide,
A refactor blooms, with style and pride.
Components align, with themes so bright,
A rabbit's work, by day and night.
Through fields of code, we hop and stride,
With styled-components, as our guide.
🌟🐾

---

Recent Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 64b0015 and d8e5913.

Files selected for processing (5)

• src/components/input/input.test.tsx (2 hunks)
• src/components/input/input.tsx (1 hunks)
• src/components/input/styles.ts (1 hunks)
• src/stories/input/input.stories.tsx (2 hunks)
• src/styles/theme.ts (1 hunks)

Files skipped from review due to trivial changes (1)

• src/stories/input/input.stories.tsx

Additional comments not posted (4)

src/components/input/input.tsx (1)

1-23: The integration of useRef for focusing on the input element, the adoption of styled-components, and the handling of additional props are correctly implemented. Good job on enhancing the component's functionality and maintainability.

src/components/input/styles.ts (1)

1-51: The restructuring of styling definitions using styled-components and the incorporation of theme-based styling are correctly implemented. The handling of disabled states with conditional styling is also well done.

src/components/input/input.test.tsx (1)

1-19: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [1-39]

The introduction of renderWithTheme for theme-based testing and the adjustments to test cases are correctly implemented. The assertions made in the test cases correctly verify the component's behavior.

src/styles/theme.ts (1)

140-145: The addition of the start function under utils.flex is correctly implemented, enhancing the theme's utility functions for more flexible layout management.

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.