docs(input): update type prop to include "file"

[not-a-ethan]

Closes # N/A

📝 Description

Updated docs for Input component as it supports type='file' per #3268

⛳️ Current behavior (updates)

Does not show that file is a valid option for type

🚀 New behavior

Does display that it is a valid option

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

No

📝 Additional Information

No

Summary by CodeRabbit

• New Features

  • Expanded the Input component to support file uploads by adding "file" as an accepted value for the type attribute.

• Documentation

  • Updated the API documentation for the Input component to reflect the new accepted values for the type attribute.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a03c52

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

[vercel]

@not-a-ethan is attempting to deploy a commit to the NextUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The pull request modifies the documentation for the Input component, specifically expanding the type attribute's accepted values to include the "file" type. This update allows the input component to support file uploads alongside the existing input types like text, email, password, and others. The change is purely documentational and does not involve any code modifications to the component's implementation.

Changes

File	Change Summary
apps/docs/content/docs/components/input.mdx	Updated type attribute documentation to include "file" as a valid input type

Suggested labels

📋 Scope : Docs

Suggested reviewers

• jrgarciadev
• wingkwong

---

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>, 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

apps/docs/content/docs/components/input.mdx (1)

334-334: Consider enhancing the documentation with file input examples.

While the type prop update is correct, the documentation would benefit from additional content:

1. Add a "File Input" example section similar to the "Password Input" section
2. Include information about file-specific features (accepted file types, size limits)
3. Document file input validation considerations

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

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 388b2ed and 0a03c52.

📒 Files selected for processing (1)

• apps/docs/content/docs/components/input.mdx (1 hunks)

🔇 Additional comments (1)

apps/docs/content/docs/components/input.mdx (1)

334-334: LGTM! Type prop updated correctly.

The addition of 'file' to the list of accepted values for the type prop is accurate and aligns with the PR objective.