Skip to content

[RFP] The Inputs Update #3094

Closed
Closed

Description

@caiotarifa

Description

Discovering Nuxt UI and Nuxt UI Pro has been one of the highlights of 2024 for me. These libraries have saved me countless hours while delivering polished, tested, and consistent components that elevate the aesthetic and functional quality of my projects. I admire the exceptional work being done by @benjamincanac and the team, particularly with the ambitious mission of rewriting the library to embrace both TailwindCSS v4 and Reka UI within Nuxt UI v3.

One of the standout features in v3 has been the integration of TanStack Tables into the UTable component, adding to tables many new features and possibilities. However, after some usage in real-world scenarios, I’ve noticed a gap: a wider variety of input components.

I know that v3 is still in alpha, but I’d like to propose a new initiative for a future release, which I’m calling "The Inputs Update". This RFP could focus on identifying and implementing input components that would further enhance the library’s usability and versatility.

Additionally, this aligns with a prior suggestion to categorize form-related components separately within the documentation (#3019).

New Components

Updates to Existing Components

  • UPinInput → UInputPin
    Rename the existing UPinInput component to align with the naming convention used across other input components.

  • UInput / UTextarea
    Add a native character counter via a counter property, configurable using the min and/or max attributes. Currently, there is an example for this functionality, but a native implementation would improve the developer experience.

Additional context

No response

Activity

  1. added
    enhancementNew feature or request
    triageAwaiting initial review and prioritization
    v3#1289
    on Jan 14, 2025
  2. zAlweNy26 commented on Jan 14, 2025

    @zAlweNy26
    Contributor

    This is awesome, nice idea!
    I have just a doubt: wouldn't it be cleaner to have UInputTime, UInputDate and UInputDateTime in just one component? Something like UInputDateTime (same name, yes) but with a prop to switch between time, date and datetime (the default).
    I'm saying that because they are pretty much the same component to me.
    What do you think about this?

  3. caiotarifa commented on Jan 14, 2025

    @caiotarifa
    ContributorAuthor

    This is awesome, nice idea! I have just a doubt: wouldn't it be cleaner to have UInputTime, UInputDate and UInputDateTime in just one component? Something like UInputDateTime (same name, yes) but with a prop to switch between time, date and datetime (the default). I'm saying that because they are pretty much the same component to me. What do you think about this?

    @zAlweNy26 That’s definitely an option worth considering, and I see where you’re coming from. However, I personally believe it’s more organized and keeps responsibilities better divided—with less logical overhead—if we have separate components. This also allows the individual "pickers" to stay modular and focused.

    A good example of this approach is the @mantine/dates library, which has been an inspiration for me. What are your thoughts on this perspective?

    https://mantine.dev/dates/getting-started/

    Image
  4. benjamincanac commented on May 14, 2025

    @benjamincanac
    Member

    Sorry for the delay on this! First of all thanks for the kind words and this proposal. We're kinda of reliant on Reka UI for those kind of components, we can only make UInputTime and UInputDate at the moment.

    I don't want to go back to logic hell like in v2 where we have enough to maintain with "styling" if I can say.

    Regarding UInputMask and UInputPhone, is it not doable already using those directives? 🤔 I'd rather keep the base components and give the flexibility to build whatever people wants.

    (I only disagree with the PinInput rename, a InputPin would be okay if there was only one input but that's not the case)

  5. caiotarifa commented on May 23, 2025

    @caiotarifa
    ContributorAuthor

    Hey, @benjamincanac.

    Regarding the month and year selector, I agree with you and will open a new issue in the Reka UI repository to request components for these controls.

    About UInputMask, UInputPhone and UInputCurrency, I really think they should be part of the core library. These are fundamental form controls that almost every web application needs, and making them available out of the box would prevent developers from reinventing the same functionality (like we have with LocaleSelect).

    Finally, renaming UPinInput to UInputPin makes sense for me from a naming-convention perspective (but that's just an opinion and I don't think it's that relevant here).


    UPDATE

    I created the feature request on Reka UI, please help leaving your 👍.

    unovue/reka-ui#1933

  6. removed
    triageAwaiting initial review and prioritization
    on May 23, 2025
  7. caiotarifa commented on Nov 19, 2025

    @caiotarifa
    ContributorAuthor

    Tip

    UInputDate and UInputTime was released on Nuxt UI v4.2.0.
    https://ui.nuxt.com/docs/components/input-date
    https://ui.nuxt.com/docs/components/input-time

    Thanks @hywax and @benjamincanac!

  8. caiotarifa commented on Dec 17, 2025

    @caiotarifa
    ContributorAuthor

    Tip

    UEditor was released on Nuxt UI v4.3.0.
    https://ui.nuxt.com/docs/components/editor

    Thanks @benjamincanac!

  9. benjamincanac commented on Mar 5, 2026

    @benjamincanac
    Member

    There are examples for mask and phone input:

    I still think it's way easier to compose like this that to create new components honestly and regarding to InputMonth and InputYear it's planned to be implemented as part of the Calendar component with a type prop: #5981

  10. github-actions commented on May 5, 2026

    @github-actions

    Hi! 👋 This issue has been open for 60 days without activity and will be closed in 7 days. Please comment if it's still relevant.

  11. added
    v4#4488
    and removed
    v3#1289
    on Jun 19, 2026
  12. locked and limited conversation to collaborators on Jun 19, 2026
  13. converted this issue into a discussion #6621 on Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featuretriageAwaiting initial review and prioritizationv4#4488

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions