[feature request] Add specific vuetify prefix to classes declarations

Adding Vuetify in an existing project causes glitches because css are not well scoped. Classes like .warning, .info or .title are really common and they shouldn’t collide.

One easy solution could be to prefix all Vuetify classes with an unique string like vtf-

[KaelWD]

I think this is done now, we won’t be changing grid or v-app for the time being.

[johnleider]

It’s something actively being worked on. The first set will be in 1.1

On Sat, Mar 24, 2018, 11:36 AM Tor Arne Vestbø [e-mail] wrote:

Is there an up to date guide on how to work around this with Vuetify 1.0.10? I’d like to use Vuetify with a-la-carte components, and have those components I import not pollute the global CSS styles, affecting nothing but their own component’s style. Is this possible through editing of e.g. the stylus rules, or some webpack plugin/module? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vuetifyjs/vuetify/issues/1561#issuecomment-375898540, or mute the thread https://github.com/notifications/unsubscribe-auth/AIpOgkngM5mkkxb5Y2X9lo1ADu2EENKnks5thmfjgaJpZM4PKNLJ .