Skip to content

Docs hard to comprehend #4863

Open
Open
@Faithfinder

Description

@Faithfinder

Provide your feedback here.

We're currently trying to build Select/MultiSelect components (which I guess you would call "TagField", when it's finally it's turn to be implemented?). React-Aria seems like the best choice feature-wise, but comprehension has been a struggle. I think I grasped the part that at the core, I just need to manage and pass around a Collection and SelectionManager, however the details are elusive.

For example: ListBox is a critical part of any such component, and is mentioned in most of relevant docs. Moreover, it's mentioned with the idea that we can build it once and just reuse. However usage examples are different in different pages:

  • Example in the useListBox itself puts useListState inside the ListBox component
  • Example in the useSelect instead passes state from useSelectState as a prop
  • We would like to allow booleans and null as possible values to be selected in the components. Seems like useListData is made for building a collection where keys need to be massaged a bit to be useable, however in that example ListBox accepts items and selectedKeys, not state.

Then, the docs menu is sorted... A bit weird? There's useSingleSelectListState at the top, but it's really just a building block for useSelectState that's at the bottom of the list?

I'm at a loss as to what pattern is suggested. Also, the types are all referencing each other. I've been staring at words List Select Props Options and State in, it seems, all possible combinations, for the last 3 days, and am feeling quite exhausted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions