Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Will the Tui framework upgrade to Vue 3?

As with all libraries, it is a good idea to upgrade them so that we receive the benefits of maintenance on those libraries. Specifically with Vue 3 there are some interesting breaking changes that were not considered at the start of the Vue 3 project. Now that Vue 3 has been released, adopters of this library will be working through these breaking changes to upgrade, finding and fixing bugs etc. There is also the much wider Vue ecosystem to consider; supporting libraries like Vuex, documentation, online community efforts, etc. There's a lot of work around the edges of the Vue 3 release that will catch issues and further improve on the 3.0 release.

When the dust settles from the initial release, the Tui framework will at that point assess the upgrade and take that step, however it will be done in a measured way.

What else will be upgraded soon?

  • Webpack 5 (October 2020) has been released which will introduce significant improvements to bundling speed and options. We will likely adopt this when that work can be prioritised.
  • Apollo Client 3 has also been released (July 2020) which introduces several benefits that are worth adopting.

How will components be upgraded or deprecated?

The Tui framework will be versioned in lockstep with Totara itself, with both minor non-breaking and breaking changes being introduced via the usual changelog and upgrade mechanisms. Until further notice we will also continue to deprecate with advance warning.

  • No labels