Fix rendering bug when switching themes about belle

[jpuri]

The reason for this issue Nik is that pseudo classes we are injecting using 'injectStyles(styles);'.
In componentWillReceiveProps we should use have:
removeStyle(this.ratingWrapperStyleId);

Before:
updatePseudoClassStyle(this._styleId, properties, this.preventFocusStyleForTouchAndClick);

Let me fix this.

[jpuri]

I have created PR: #103
There might be issues other than these also with styling, we can test more.

[nikgraf]

good find, unfortunately it's still a problem because pseudoClass styles are only updated in the constructor or willReceiveProperties. We just call render on theme switch right now. I'm not sure we even want to handle the case people changing the config on the fly properly. As an alternative we could have a query string in the route & based on this decide the theme. When someone changes the theme we switch the URL & do a window.location.reload()

[jpuri]

Yep we can fix issue in docs by using window.location.reload() and I think the probably of users changing themes on fly is very low.

But @nikgraf , if I think from the perspective of good code structure....if theme can change dynamically its not good to bring them in react components with just
import style from '../style/button';

Probably a design like this which Vjeux told would be better:

belleComponents = new BelleComponents(stylingTheme)

Also, React component should ideally change only by user interaction or change in props..... this 'forceUpdate()' brings a feeling of something done wrong. And variables other than state and props are affecting the component.

[jpuri]

This way to configuring by changing core configurations in lib do not look good:

belle.style.button.style = _.extend(belle.style.button.style, {
color: '#FFF',
background: '#444',
border: '1px solid #444',
borderBottomColor: '#000'
});

[nikgraf]

Hmmm, we can provide an extra API, but I had the feeling it's not necessary. The idea was that if we have simple plain JS objects then people are familiar with it & can overwrite or extend them depending on what they want.

[nikgraf]

I think the API Vjeux proposed to create multiple stylings on one page would still be nice on top of the existing API. I fell we still should stick to the commonJS API use-case. That's what JS people are used to.

[nikgraf]

Fixed with this PR: #109