Stew Heckenberg

Guessing it should be `'class': String` instead?

@Remo see also https://github.com/chenz24/vue-blu/issues/56 -- it's not a trivial task giving the changes from 0.3 to 0.4 of Bulma. I guess it'll happen when @chenz24 has some time :)

This is what you see if you use the class binding above:  It binds to the span which wraps the input.

Sorry, I forgot to mention I'm using Vuelidate for validation. I just realised it's producing that console warning. So what's happening is that if I select/highlight the number in the...

I've actually worked out a fix I can use to avoid the error: `` :val="foo" :on-change="function(n) { foo = parseInt(n); $v.foo.$touch() }" `` This ensures that the value of `foo`...

I've come up with a workaround (or maybe this is the right way to do it?) by giving the modal/aside a ref attribute, e.g. `

@stvnmoon I don't think he did, and I don't think it would work without @chenz24 updating the various Vue Blu component HTML markup.

Actually, instead of `this.location.place.formatted_address` it might be preferable to use `this.location.place.name` for things like businesses or landmarks etc. Or you could use both like "name, address": ``` this.search = this.location.place.name...

Related, tooltip will show for attribute syntax but only if class names are not on the same line as the element, e.g. ``` div( shrink-0 w-4 ) ``` or if...

Sorry @PieroJacinto I'm no longer working on the project that was using this.