Migrate all MarkBind components from vue-strap to bootstrap-vue

[luyangkenneth]

The end goal here is to remove our dependency on vue-strap altogether. This is a major investment, so the team will have to make the choice of whether (or better yet, when) to prioritize this over feature work.

Related discussion:

• Explore the feasibility of merging vue-strap into the MarkBind repository #411 illustrates the inconveniences of working with vue-strap
• Alternatives for MarkBind components #245 discusses the incentives of such a migration and what work it will involve

[damithc]

Would this solve FOUC problem?

[yamgent]

Would this solve FOUC problem?

No, bootstrap-vue doesn't have anti-FOUC mechanisms.

[damithc]

Which components are pending migration?

[Chng-Zhi-Xuan]

Instead of modifying our current files Vue.js component files, I suggest we fork Bootstrap-Vue (removing vue-strap dependencies + security vulnerabilities) and start building templates to preserve MarkBind syntax.

If we were to take this approach, all the common components (e.g popover/tooltips) will need their own template. Components that do not exist in Bootstrap-Vue such as panels, would have to be re-written (with the existing vue-strap code to serve as a guide).

[nbriannl]

May I clarify if this direction to migrate to bootstrap-vue is still actively being pursued? Or are we deciding to stick with our fork of VueStrap? Considerable improvements have been made so far especially updating of dependencies MarkBind/vue-strap#130.

I was considering to investigate and possibly implement some PRs for vue-strap related to testing, but if the end goal is still bootstrap-vue then I'll divert my efforts elsewhere. 🙂

[ang-zeyu]

Reopening since it was mistakenly closed in #1033 - only popovers, modals, triggers, tooltips are migrated