I removed a reset by clicking on non-sortable column, because it just set sortBy to null, but parameter sort=null|<sortDesc>still sending to backend API.
On another tought, is may be up to Item provider func to deal with null sort target and remove it from query.
And on third thought, maybe better not expicitly to null sortBy, but reset it to default sortBy, defined at startup. If it not defined, then to null it.

Although some may want to clear the sort... but you never know. The original table (from before I started working on it) cleared the sort on a non-sortable column.

Some people may want to table to display in the order sent from the server (as not having a null sort by would case b-table to sort the data which is received).

Yep, i think that this feature should be restored at my variant of <b-table>
But it needs to be reviewed.

I think, we can merge this branch, and i will continue to work on mine.

OK cool... so everything looks OK in this branch?

Mmm, Ill make a final test at local Playground doc, though

OK good... The docs example should show the sort key and order under the table, using the .sync modifier.

Also, I could dd a button that says 'clear sort' (which is disabled if sort-by is null) to the example.

Clicking on the button would set sort-by to null, and if sort-by is null then the button could be disabled. Sowing a bit more interactivity with with the table.