vouill / vue-bulma-components Goto Github PK

For example I want to have a component that changes it's class based on a value

I could do <b-button is-small :is-danger="notConnected" :is-success="connected" />, but is there a way to do <b-button is-small :class="connectedClass"> without overriding the already specified classes?

Hi, I was just checking pull request #8 is already merged and I tried to update vue-bulma-components to version 1.7.0 on my project. However, I don't think the build lib is updated to version 1.7.0, its still using version 1.6.0. Please kindly check, thanks!

Hello maintainers

I am interested in making use of this as part of a Uni project, but there is no defined licence, so opensource.stackexchange.com suggests that all rights are reserved. Is this the case? If so is there a point of contact regarding use?

https://opensource.stackexchange.com/questions/1720/what-can-i-assume-if-a-publicly-published-project-has-no-license

Many thanks

Hey !

I am thinking about 2.0, i would like to tackle few things with vue-bulma-components.

• See if we can simplify the code base ?
• Better contributing doc

Also:

• I would like to change the way the components are being called.
  Right now, if we add all components, we can have this:

<box is-primary />
<b-input is-loading/>

The issue i see here is how the component name do not follow the same pattern.
One sticks to bulma names, the other have a predefined prefix to it.

More over, i believe it's better to know that we are using a component coming from X library just by using it.

A good example of what i am trying to say is vuetify:

<v-content>
<v-####>

What if we alway prefix bulma components in the same way:

<b-box is-primary />
<b-input is-loading/>

It will be much easier to split dumb/visual/library components and logic/your own components too.

The only issues:

Will break users code if they use Vue.use(defaultImport).
<box /> will have to be changed to <b-box />

Possible solution? :
Handling both cases and add a deprecation warning in the log.

What do you guys think ?

Hi,
Just started getting into vue and bulma, stumbled upon this project and very much like it. I'm running into an issue where CamelCaseToDash has an issue handling image attributes such as is-128x128

Expected:
<b-image is-128x128> --> <figure class="image is-128x128">
Result:
<b-image is-128x128> --> <figure class="image is-128x-128">

I'm guess camelCaseToDash is seeing 128x128 and assuming it is to be separated.