Christhofer Natalius
Christhofer Natalius
I do use purge as the docs says ` purge: [ './src/**/*.vue', ], ` I just think that maybe it'd be useful to have configurable option.
This problem still exists. Any workaround?
Oh I almost create a new issue about this problem. I experience the same with indonesian language.
> You can use class binding and compare it with your routes > > ``` > to="/purchase/purchase-request" > class="btn" > :class="{'btn-secondary': this.$route.path != '/purchase/purchase-request'}" > active-class="btn-primary"> > Purchase Request >...
> Add a regular class to those specific links and override them with the active class: `class="btn btn-secondary" active-class="btn-primary"` @posva but that will be rendered as `class="btn btn-secondary btn-primary"` instead...
I don't quite understand the confusion about this request. High prio high complex? Vue-router already know when to append active class Can't we just make it a simple ternary `isActive...
If we can get the active / exactActive value from vue router, I'm fine with custom component that wraps router link component. I wrapped all of my components that comes...
Now that Laravel 8 uses Tailwind as the default, this use case should becomes more common, isn't it? > I mean creating a custom component that extends router link so...
> since this solution works on Vue router for Vue 2 Got it. Will try this in my next project.
@posva , I see that $listeners is deprecated in vue 3. Any alternative for this? I can't find about it in v3 docs.