Fix Unit tests and useI18n() misuseVue 3's vue-i18n requires useI18n() to be called within setup()or reactive contexts. Calling it in Options API data() createsdisconnected i18n instances that ca
Fix Unit tests and useI18n() misuseVue 3's vue-i18n requires useI18n() to be called within setup()or reactive contexts. Calling it in Options API data() createsdisconnected i18n instances that cannot resolve linked messages.Component fixes:- Enable globalInjection in i18n.js for automatic $t injection- Remove explicit useI18n() imports from 84 components that incorrectly called useI18n().t in their data() functionsUnit test fixes:- Mock @/i18n module in jest.setup.js because Webpack's require.context() does not work in Jest, leaving the real module with no locale messages loaded- Re-export real createI18nInstance so i18n unit tests work- Update snapshots to reflect real translated text instead of raw translation keys- Fix b-form-radio/checkbox stubs to wrap content in div for proper data-test-id attribute inheritance- Remove duplicate i18n plugin installations from individual test files that caused 'already registered' warnings- Suppress expected missing-key warning in vendor overlay testTested:- Sanity testing on webui, ensured translations work.- All Unit tests pass (19/19) with no Errors or Warnings.Change-Id: I9789acd823261eccc7affde0957dd22e8fec06b1Signed-off-by: Jason Westover <jwestover@nvidia.com>
show more ...
Vuelidate, I18n, and filter are upgraded to vue3While navigating to the pages i18n, vuelidate, and filters errorsoccurred. i18n, and vuelidate code changes in each page adapted tovue3. Filter glo
Vuelidate, I18n, and filter are upgraded to vue3While navigating to the pages i18n, vuelidate, and filters errorsoccurred. i18n, and vuelidate code changes in each page adapted tovue3. Filter global function for date and time format implementedin the main.js file and those files which as called the filterfunctions.Change-Id: If1a2ee22d47750faef1c35ef2c263299067d9a20Signed-off-by: Surya Venkatesan <suryav@ami.com>
Update linting packages to use latest- 99% of changes were small syntax changes that were changed by thelint command. There were a couple of small manual changes to meet theproperty order pattern
Update linting packages to use latest- 99% of changes were small syntax changes that were changed by thelint command. There were a couple of small manual changes to meet theproperty order patterns established as part of the vue:recommendedguidelines.There are rules that were set from errors to warnings and new storiesare being opened to address those issues.Testing:- Successfully ran npm run serve- Successfully ran npm run lint- Verified functionality works as expected, e.g. success and failure use cases- Resolved any JavaScript errors thrown to the consoleSigned-off-by: Derick Montague <derick.montague@ibm.com>Change-Id: Ie082f31c73ccbe8a60afa8f88a9ef6dbf33d9fd2
Add 404 page- User will be redirected to 404 page when navigating to undefined routesSigned-off-by: Dixsie Wolmers <dixsie@ibm.com>Change-Id: I5d7bbcfdd279b6f6c993370e3adb39a516dbb1ba