Skip to content

Commit 54fa3f8

Browse files
authored
Release 0.21.0 (#626)
* Vue 3 Migration (#620) This PR is to upgrade the existing solution and relevant dependencies to Vue 3. Because we are also migrating from Vuetify 1.5 -> 3 in the process, skipping over Vuetify 2 entirely, every component required some clean-up. The goal was to get parity in UI from the previous release, which included some new CSS rules to maintain the look at feel of the previous UI. These changes are likely to result in breaking changes to custom CSS modules, though again we have tried to maintain as much parity as possible its not feasible to test every CSS iteration end users might have implemented. Please use caution when updating to this version of the UI. --------- Co-authored-by: Austin Johnson <[email protected]>, @michaelin-96
1 parent 82a620f commit 54fa3f8

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

49 files changed

+13079
-27509
lines changed

CHANGELOG.md

+3
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ All notable changes to this project will be documented in this file.
44
The format is based on [Keep a Changelog](http://keepachangelog.com/)
55
and this project adheres to [Semantic Versioning](http://semver.org/).
66

7+
## [0.21.0] - 2024-03-01
8+
- Upgraded the existing solution and relevant dependencies to Vue 3. Migrating from Vuetify 1.5 -> 3 in the process, skipping over Vuetify 2 entirely, requiring clean-up and reconfiguration of all UI components. Goal was to get parity in UI from the previous release, which includes some new CSS rules to maintain the look at feel of the previous UI. These changes could result in **breaking changes** to custom CSS despite efforts to maintain backwards compatibilty many Vuetify classes changed names during the upgrade. Please use caution when updating to this version of the Lex Web UI UI.
9+
710
## [0.20.6] - 2024-02-12
811
- Emergency fix to upgrade Python function to version 3.8 across the board. As this will end of life later in the year we will release another update soon to move everything to 3.12.
912

README-css-style.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -80,9 +80,9 @@ There are two distinct mechanisms for changing the background color.
8080
1) Update lex-web-ui-loader-config.json. Change the property ui.toolbarColor. You must select a value
8181
from.
8282
https://vuetifyjs.com/en/styles/colors#
83-
2) OR use the following in css
83+
2) OR use the following in css to overwrite the color of the default red CSS
8484
```
85-
.toolbar.theme--dark {
85+
.bg-red {
8686
background-color: #2b2b2b !important;
8787
}
8888
```

build/create-custom-css.js

+1-1
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ if (process.env['CHAT_BACKGROUND_COLOR'] && process.env['CHAT_BACKGROUND_COLOR']
5252
modifyRule(styleSheet, '.message-list-container', { "background-color": process.env['CHAT_BACKGROUND_COLOR'] + ' !important'});
5353
}
5454
if (process.env['TOOLBAR_COLOR'] && process.env['TOOLBAR_COLOR'].length > 0) {
55-
modifyRule(styleSheet, '.toolbar.theme--dark', { "background-color": process.env['TOOLBAR_COLOR'] + ' !important'});
55+
modifyRule(styleSheet, '.bg-red', { "background-color": process.env['TOOLBAR_COLOR'] + ' !important'});
5656
}
5757
if (process.env['AGENT_CHAT_BUBBLE'] && process.env['AGENT_CHAT_BUBBLE'].length > 0) {
5858
modifyRule(styleSheet, '.message-bot .message-bubble', { "background-color": process.env['AGENT_CHAT_BUBBLE'] + ' !important'});

dist/0.17.7_dist_vuetify.min.css

-7
This file was deleted.

dist/0.17.7_dist_vuetify.min.js

-6
This file was deleted.

dist/2.6.11_dist_vue.min.js

-6
This file was deleted.

dist/3.3.10_dist_vue.global.prod.js

+6
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

dist/3.4.0_dist_vuex.min.js

-6
This file was deleted.

dist/3.4.6_dist_vuetify.min.css

+12
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)