BMC/OpenBmc/webui-vue.git/src/views/Settings/PowerRestorePolicy, branch master

Revert policy selection on save error

2026-09-15T06:29:40+00:00

When a readonly user changes the policy and clicks save, the failed request left the radio group stuck on the new selection. Replace the split computed getter/setter with a local `selectedPolicy` data property and explicitly reset it to the store value on error. Change-Id: I1785384f0a654c8daa447a70e44336bb22ffa4d2 Signed-off-by: Vedangi Mittal

Fix Unit tests and useI18n() misuse

2026-01-13T21:32:20+00:00

Vue 3's vue-i18n requires useI18n() to be called within setup() or reactive contexts. Calling it in Options API data() creates disconnected 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() functions Unit 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 test Tested: - Sanity testing on webui, ensured translations work. - All Unit tests pass (19/19) with no Errors or Warnings. Change-Id: I9789acd823261eccc7affde0957dd22e8fec06b1 Signed-off-by: Jason Westover

Vuelidate, I18n, and filter are upgraded to vue3

2024-10-03T18:34:06+00:00

While navigating to the pages i18n, vuelidate, and filters errors occurred. i18n, and vuelidate code changes in each page adapted to vue3. Filter global function for date and time format implemented in the main.js file and those files which as called the filter functions. Change-Id: If1a2ee22d47750faef1c35ef2c263299067d9a20 Signed-off-by: Surya Venkatesan

Upgrade vue3 and all dependencies

2024-10-03T18:34:06+00:00

Start the process of porting everything to Vue 3. I have most things working. npm run-scripts build works, npm install works. prettier passes. Styles load, login works, webui loads. This was primarily done using the linked documents below. It makes the following design decisions: 1. Vue is put in compat 2 mode, which allows most of the components to work as-is. 2. Bootstrap v4 is used along with bootstrap-vue to keep our components working. 3. Minor changes are made to load the latest versions of vue-router, vuex, and vue-i18n. I suspect this patchset is good enough to start with, and we can clean up the broken things one patchset at a time. The things that need to happen are: 1. Get remaining features working again. This primiarily is vue-i18n for mixins, and non vue components. This likely needs to be done by not pulling in i18n into the non vue components, then using the .Vue files to do the internationalization in the component context, NOT in the mixin context. Alternatively, we could drop MixIns alltogether. 2. Get custom styles working again. Previously, we used some path hackery in vue.config.js to optionally pre-load styles. This stops working now that we're required to @import our modules. Likely we need some rearangement of the paths such that custom styles are a complete replacement (possibly importing the original) rather than additive with overrides. That's a guess, but I don't really see anyone else doing customization the way we've defined it here. 3. Bootstrap 5 no longer requires ANY custom vue modules, as it has dropped the jquery dependency. We won't be able to pull in bootstrap 5 all at once, so pull in bootstrap 5 under an alias, like "bootstrap5" that we can optionally import 5 or 4. 4. One at a time, start porting components over to Vue3 syntax and bootstrap 5. This will be the bulk of the manual work and review. The only thing I think left is getting unit tests passing, which I commented out the pre-commit hook to make this PR. Tested: Code builds. Needs better testing. [1] https://router.vuejs.org/guide/migration/ [2] https://vue-i18n.intlify.dev/guide/migration/vue3 [3] https://vuelidate-next.netlify.app/migration_guide.html#package-name-and-imports Change-Id: I5bb3187b9efbf2e4ff63e57994bc528756e2a981 Signed-off-by: Ed Tanous

Fixed radio buttons arrangement issue

2024-05-09T08:40:44+00:00

- The contents in the Power restore policies were not listed in a new line for large or extra large screens, Fixed this by using stacked prop. Signed-off-by: Nikhil Ashoka Change-Id: I30ec1206a929137fc6635d602944cd80d2c2805f

Reformat files with new linter

2024-03-05T04:23:10+00:00

All changes should be whitespace, and were done using npm run-script lint. Change-Id: I943c6b435c5c872841af5affc1e89910468b5ca6 Signed-off-by: Ed Tanous

Re-modeled Power restore radio buttons

2022-02-04T16:29:18+00:00

When a user selects a radio button and saves, the selected setting should be patched. - Computed properties on generated bootstrap-vue radio buttons causes errors. - Re-modeled radio buttons to take Redfish api data on component render. - Mapped selected radio button value to patch the Redfish api property. - Added translations. Signed-off-by: Kenneth Fullbright Change-Id: I22ce75d9ef840d7f0c2659bba855093e5b4559f4

IA update: Update configuration to settings

2021-08-10T19:20:42+00:00

This is the fourth update to information architecture changes and has the following changes: - The configuration section is updated to settings - The date and time settings page is updated to date and time - The network settings page is updated to network - The power restore policy page in operations section is moved to settings section Signed-off-by: Sandeepa Singh Change-Id: I6f5ab25f5227530be430bd39a4d9629b3bf09d8b