Issayah
Issayah
> Just a brief note on that noTrap prop, will the focus-trap reactivate upon toggling it back on? Feel free to ignore this question. I didn't add this, mostly because...
It appears this https://github.com/bootstrap-vue-next/bootstrap-vue-next/issues/1798#issuecomment-1970397987 is the correct behavior. With the change to `sortBy` becoming a v-modelable value, one could use that to determine when sort has changed (@update:sort-by). Alternatively, the...
(Keep in mind, I'm not quite sure how to fix this so any help is appreciated)
> simply not yet implemented? This
The typing didn't change in the library. What did change was Vue 3.3. In Vue 3.3 defineSlots was introduced. I'm suspecting the default transitioned from "any" to "unknown". Plans to...
And during that period _we_ updated to Vue 3.3
Though generics are possible with 3.3, they are in a buggy state which makes them near impossible to use.
You could make a PR that adds defineSlots to each of the tables without generics and just set the output to any. Just keep in mind the inheritance as things...
Also the props are fine ideas. There are some bootstrap-vue components that use similar sounding props, to where it's essentially `:model-value="true"`, I removed them because it was like a second...
This is by design, but I wonder if there should be a "icon-direction" slot scope