Haz

Conversation on Twitter: @diegohaz: Start by creating an app on Facebook and grabbing a test user access token. @chaurasiagovind: Where to keep that token on server. And where to pass...

If `ref` is going to be part of props, will it be considered by `React.memo`? If so, what about refs passed as inline functions?

Try to pass the store directly to CompositeItem instead of relying on CompositeProvider.

We have scoping on most components. We just don't check it on CompositeItem because it's too low level and most of the time people use it with the composite store...

@DaniGuardiola Sure, I think this should be fixed in CompositeItem. Usually, using useCompositeProviderContext instead of just useCompositeContext is enough. I don't have my computer right now, but I believe MenuButton...

Workaround: ```jsx const radio = Ariakit.useRadioStore(); ... { const checked = store.getState().value === "a"; if (checked) { // Avoid triggering onChange on focus when the radio button is already checked...

Thanks for tackling this, @bengry! I think this implementation might introduce a breaking change, as some folks could expect the `anchorElement` state in the popover store to reference the disclosure...

[We still don't have examples/tests with array fields](https://github.com/ariakit/ariakit/issues/939#:~:text=Form%20with%20array%20fields), so I think creating one with some tests would be a good starting point.

Revisiting Form is planned before launching v1. [As I mentioned](https://github.com/ariakit/ariakit/issues/3607#issuecomment-2016715896), we still need examples with automated tests using array fields. I'm also waiting for React/Next.js to release the full story...

Probably related to #3402