github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 15:54:15 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

[PR #6724] [MERGED] feat: Add tooltips to provide contextual information for each parameter #8736

New Issue
Closed
opened 2025-11-11 18:04:40 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 18:04:40 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/6724
Author: @silentoplayz
Created: 11/5/2024
Status: ✅ Merged
Merged: 11/5/2024
Merged by: @tjbck

Base: dev ← Head: silentoplayz-tooltips

📝 Commits (4)

  • 8c1983c Update AdvancedParams.svelte
  • e5f9ef4 Update AdvancedParams.svelte
  • 634be4a Update AdvancedParams.svelte
  • cd6e05d Update AdvancedParams.svelte

📊 Changes

1 file changed (+320 additions, -169 deletions)

View changed files

📝 src/lib/components/chat/Settings/Advanced/AdvancedParams.svelte (+320 -169)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests for validating the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

  • Added tooltips to AdvancedParams.svelte to provide contextual information for each parameter, enhancing user experience and understanding.

Added

  • Tooltips for parameters in src/lib/components/chat/Settings/Advanced/AdvancedParams.svelte.

Additional Information

  • This change aims to improve the overall user experience and provide context for each parameter in the Advanced Parameters section.
  • No new dependencies or breaking changes are introduced in this pull request.
  • Tooltip content strings have been "i18n"ized with this PR. What I do not know how to do is ensuring those strings can be translated directly into other languages. I know each translation.json file would need updated to store the new strings, but that seems like a real tedious task that in which I don't know how to automate.

Screenshots or Videos

image
image
image

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/6724 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 11/5/2024 **Status:** ✅ Merged **Merged:** 11/5/2024 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `silentoplayz-tooltips` --- ### 📝 Commits (4) - [`8c1983c`](https://github.com/open-webui/open-webui/commit/8c1983cfda5d2b8b9f6400944a14ec900a450b03) Update AdvancedParams.svelte - [`e5f9ef4`](https://github.com/open-webui/open-webui/commit/e5f9ef45154d51de4d0ea1b8217932bfa064e57f) Update AdvancedParams.svelte - [`634be4a`](https://github.com/open-webui/open-webui/commit/634be4a97ade7d7c757bf45e3db6b401c4846aec) Update AdvancedParams.svelte - [`cd6e05d`](https://github.com/open-webui/open-webui/commit/cd6e05d43c828cc2774d468fb10a94ee5b42575f) Update AdvancedParams.svelte ### 📊 Changes **1 file changed** (+320 additions, -169 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/components/chat/Settings/Advanced/AdvancedParams.svelte` (+320 -169) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests for validating the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To cleary categorize this pull request, prefix the pull request title, using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - Added tooltips to `AdvancedParams.svelte` to provide contextual information for each parameter, enhancing user experience and understanding. ### Added - Tooltips for parameters in `src/lib/components/chat/Settings/Advanced/AdvancedParams.svelte`. --- ### Additional Information - This change aims to improve the overall user experience and provide context for each parameter in the Advanced Parameters section. - No new dependencies or breaking changes are introduced in this pull request. - Tooltip content strings have been "i18n"ized with this PR. What I do not know how to do is ensuring those strings can be translated directly into other languages. I know each translation.json file would need updated to store the new strings, but that seems like a real tedious task that in which I don't know how to automate. ### Screenshots or Videos ![image](https://github.com/user-attachments/assets/0ffb28ab-21ba-42c6-b70c-0e7e9b22aaf6) ![image](https://github.com/user-attachments/assets/d8b3d7cc-1998-4e38-8af9-7953a731b3d0) ![image](https://github.com/user-attachments/assets/15e82c87-5a98-41d3-a8e9-1dd53080a6f9) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-11 18:04:40 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#8736
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?