Missing feature is from

bootstrap-vue

Docs

https://bootstrap-vue.org/docs/components/table#v-model-binding

Describe the missing feature

• From my reading BSV used v-model in a kind of kludgy way to expose the rows that it's currently displaying. I don't think we should re-implement that, but it might be useful to expose computedDisplayItems - I think that would serve the same purpose and be considerably cleaner.
• When writing the stub description of the default compare, I just hand-waved over getStringValue - I wonder if it's worth exposing this somehow? Since were not adding all the bells and whistles to modify the default compare (allowing the user to specify locale and options), it seems like it would be worthwhile to make it easy to re-implement the default with different values and exposing getStringValue would be a key part of that.