Laura Beatris

Transitions e Data Fetching com Suspense API no React 18

Hey @jithureddy, thanks for creating this issue! I think that the current behavior is correct but there are use cases, like the one you mentioned, in which `all` should be...

Hey @tlindener, thanks for reporting this issue! I'm mostly sure it's related to a truthy check on the `items` value when updating it - I'll double-check that and open a...

Hey @smooJitter Thanks for the amazing feature request I'll definitely add it to the backlog!

@rodrigogama Thanks 😄 > I'd be glad to help you with this issue. How do you think we should address the solution? Should we put this logic inside the reducer...

@gabrielnaoto Thanks for the comment! > I agree that this prop name, is not very intuitive. I think it could be something like allowToggleNext. ``allowToggleNext`` or ``shouldToggleNext`` are both intuitive...

> Another point is that, in order to allow toggling the last selected items I think we would need to have some type of queue to track the order on...

> When toggling all items, if there's one selected, should we just invert the selection, or instead, should we firstly select all items (if there are some not selected), and...

Alright! Thanks, everybody for sending suggestions. I'll start working on it ASAP 🔥

We might verify the field name before doing any calculations with it. Using an inline condition in one of the functions, do not cover all the cases that are using...