Benoît Burgener
Benoît Burgener
Sorry, I forgot to mention the repository where this happens is public: https://github.com/liip/styleguide I tried to add the returns but it didn't solve the issue. I just saw that we...
The following warning: > [0] Could not find the language 'text', did you forget to load/include a language module? Has been fixed by #579
This package is not published on the npm registry, it gets installed by npm through Git. Try to install Git first.
There’s indeed an issue with this, when you provide `vuetify` object globally through a decorator, it works once (its defined the first time it goes through the function), but then...
@pocka Isn’t the decorator needed in any case? The components must be wrapped within a `VApp` element for the styling to be applied properly. Also passing the Vuetify instance to...
I had the same issue yesterday and this morning, after a while I pull to refresh and it worked. While browsing, it came back to "offline" for a while and...
Thanks for the tip! The same problem occurs with radios by the way.
I also got confused because GitHub says latest is 2.x and composer doesn’t bring it up when running `outdated`. All good now using 3.x
I suppose this is a problem related to Parse in general, I’ve got [a similar issue](http://stackoverflow.com/questions/34493769/react-component-fetching-parse-object-with-relations-get-the-wrong-classname) without using ParseReact.