Hooks 🎉

[CarsonF]

useSplitTreatment

const [treatment, config] = useSplitTreatment('my-split', { optionalAttributes });
return treatment === 'on' ? <MyFeature /> : null;

I didn't see a need to include multiple splits because the hook can just be called multiple times, which is inline with what React suggests.
Maybe it would be good to return it as an array/tuple instead that way the individual treatments can be relabeled easier? Changed to that.

useSplitTrack

// Same track function as the client has
const track = useSplitTrack();
const handleClick = () => {
  track('button_clicked', ...);
};

Maybe useTrack would be better? And if it's ambiguous people can rename on import? I guess same goes for the other hook too.

[CarsonF]

This kinda depends on #2, but I know that one has breaking changes. If we want this to go in first I should change the client check.

[samuelcastro]

It looks great, you mentioned breaking changes, do we have any breaking changes here?

[CarsonF]

None here 😄

[samuelcastro]

Another thing, we need to update the README to include the hooks usage, could you do that?

[CarsonF]

Added docs and renamed the hooks.

We might still have a discrepancy with what's returned by default from useSplit and Split, the "control" vs null thing.

[samuelcastro]

Great!