Add backwards compatibility to Ariakit implementation of Composite

[andrewhayward]

What problem does this address?

The last step in migrating from reakit to ariakit (#53278) is to drop support in Composite. All of the consumers of the reakit implementation have been migrated, so now we need to remove the implementation. The first step in doing this is to ensure API compatibility.

What is your proposed solution?

In order to make the public migration smoother, we should implement support in the ariakit implementation for the reakit API. The only part currently missing is useCompositeState (ref).

As per these thoughts on the matter, it will involve the following...

function convertInput(props) {
  ...
}

function convertOutput(props) {
  ...
}

function useCompositeState(props) {
  const store = useCompositeStore(convertInput(props));
  const state = store.useState();
  return convertOutput({ ...store, ...state });
}

...where the implementation of convertInput and convertOutput will need to reference Reakit's useCompositeState API reference and Ariakit's useCompositeStore API reference for the differences.

Actions

• Write unit test to confirm current useCompositeState functionality
  • Adding unit tests for useCompositeState to Composite component #56645
• Implement useCompositeState using Ariakit, as above
  • Implementing useCompositeState with Ariakit #57304

[andrewhayward]

Closed by #57304.