Allows arbitrary components anywhere inside <TabList>

[alexanderwallin]

This is a follow-up feature to #123, which allowed adding arbitrary components after a <TabList>'s <Tab>s.

Now you can put components anywhere inside <TabList> and everything should work as expected.

My use case was that I needed a logo-ish before the tabs. Tab group separators is another example.

[danez]

Thanks for your contribution. What happened when you where trying to add a dom node infront of the tabs? did it crash?

[alexanderwallin]

The index was offset by 1 for each node, so with one preceding node the tab left to the one clicked would be selected. Also, navigating with the keyboard broke as the number of tabs (getTabsCount()) was incorrect.

I am getting an invariant error, though:

invariant.js:38 Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's `render` method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).

[alexanderwallin]

The invariant error seems to occur when I symlink my local fork of react-tabs using either npm link react-tabs or a Webpack alias.

Weird! Don't really know what's happening.

[alexanderwallin]

Would be great if someone would try this out!

[alexanderwallin]

Let me know if you need an extra hand reviewing issues and PRs, @danez!

[tazcarper]

Was this ever pulled into master? Any updates on it?

[danez]

Merged with 0a15604

[alexanderwallin]

Sweet, @danez! Just out of curiosity, why not merge normally?

[danez]

I merged a lot of other changes before (especially the rewrite to native classes) and so everything was a conflict and I had to pick by hand.
Sorry that you are not in the git history now, but will mention everyone in the changelog.

[alexanderwallin]

Ah, I see. No need to apologise, I was just interested in the circumstances. :)