Is 'getCollectionNode()' a public stable interface for Collections? #6341
Closed
nicholasrice
started this conversation in
General
Replies: 1 comment 1 reply
-
In general, no. We don't publicly document it and don't consider it a public API. That said, it hasn't changed in a long time. We do hope to eventually have a public Collection implementation, but it's likely to be the one from RAC. Though you may find you don't need to do anything so complex if you are using RAC. https://react-spectrum.adobe.com/react-aria/Select.html#reusable-wrappers And there's some work on exposing custom renderers here Add support for custom collection renderers (e.g. virtualization) which may further mitigate your issues |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! First, thanks for all your hard work on react-aria, we're really enjoying using it :)
I'm working on a UI library that is using react-aria and react-stately hooks for most of the business logic. We're looking to create some proprietary Collection Item types. Internally, I see prolific use of getCollectionNode which seems to be the main interface for interacting a Collection, however I don't see
getCollectionNode()
exposed publicly, nor is it referenced in documentation as far as I can tell. IsgetCollectionNode()
a stable interface that should be used for building proprietary Item types, or is that a private implementation detail of react-aria that shouldn't be used by library consumers?Beta Was this translation helpful? Give feedback.
All reactions