mirror of
https://github.com/open-webui/open-webui.git
synced 2026-06-03 07:24:59 -05:00
[PR #20453] [CLOSED] refactor: extract showSuccessToast helper in Settings #96666
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/20453
Author: @silentoplayz
Created: 1/7/2026
Status: ❌ Closed
Base:
dev← Head:refactor/settings-toast📝 Commits (1)
d9c6f40refactor(admin): extract showSuccessToast helper in Settings📊 Changes
1 file changed (+14 additions, -10 deletions)
View changed files
📝
src/lib/components/admin/Settings.svelte(+14 -10)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
Before submitting, make sure you've checked the following:
devbranch. Not targeting thedevbranch will lead to immediate closure of the PR.Changelog Entry
Description
Refactored the Admin Settings component to reduce code duplication by extracting repeated toast notifications into a helper function.
Added
showSuccessToasthelper function inSettings.svelteto standardize success messages.Changed
toast.success($i18n.t('Settings saved successfully!'))with the new valid helper function.Removed
Additional Information
This change addresses a DRY (Don't Repeat Yourself) violation in the settings component where the same toast message logic was repeated multiple times. It makes future updates to the success message easier as it's now defined in a single location.
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.