[PR #17810] [CLOSED] Fix/typescript import errors #40187

Closed
opened 2026-04-25 12:35:45 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/17810
Author: @BABz84
Created: 9/27/2025
Status: Closed

Base: mainHead: fix/typescript-import-errors


📝 Commits (2)

  • bd50dc4 Merge local ORCA changes onto upstream
  • 4eafac6 fix: resolve TypeScript import errors and create missing implementation files

📊 Changes

217 files changed (+10388 additions, -8397 deletions)

View changed files

📝 .env.example (+6 -1)
📝 CHANGELOG.md (+0 -54)
DEPENDENCY_SETUP_COMPLETE.md (+76 -0)
ORCA_PROJECT_PLAN.md (+1162 -0)
ORCA_REAL_ESTATE_AI_PRD.md (+520 -0)
ORCA_REAL_ESTATE_PRD.md (+686 -0)
backend/data/readme.txt (+0 -1)
📝 backend/open_webui/config.py (+24 -19)
backend/open_webui/data/readme.txt (+0 -1)
📝 backend/open_webui/env.py (+3 -7)
📝 backend/open_webui/functions.py (+1 -1)
📝 backend/open_webui/main.py (+11 -104)
📝 backend/open_webui/models/channels.py (+0 -4)
📝 backend/open_webui/models/chats.py (+1 -16)
📝 backend/open_webui/models/files.py (+0 -11)
📝 backend/open_webui/models/notes.py (+8 -61)
📝 backend/open_webui/models/oauth_sessions.py (+0 -20)
📝 backend/open_webui/models/tools.py (+0 -2)
📝 backend/open_webui/retrieval/utils.py (+1 -7)
backend/open_webui/retrieval/web/ollama.py (+0 -51)

...and 80 more files

📄 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 to validate 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 clearly 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

  • [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

  • [List any new features, functionalities, or additions]

Changed

  • [List any changes, updates, refactorings, or optimizations]

Deprecated

  • [List any deprecated functionality or features that have been removed]

Removed

  • [List any removed features, files, or functionalities]

Fixed

  • [List any fixes, corrections, or bug fixes]

Security

  • [List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

  • BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

  • [Insert any additional context, notes, or explanations for the changes]
    • [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

  • [Attach any relevant screenshots or videos demonstrating the changes]

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.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/17810 **Author:** [@BABz84](https://github.com/BABz84) **Created:** 9/27/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/typescript-import-errors` --- ### 📝 Commits (2) - [`bd50dc4`](https://github.com/open-webui/open-webui/commit/bd50dc41d0d60d22fe8a023db2c31bfa17a9b023) Merge local ORCA changes onto upstream - [`4eafac6`](https://github.com/open-webui/open-webui/commit/4eafac660e5a9610fe4b071b696ac4edd1d07c93) fix: resolve TypeScript import errors and create missing implementation files ### 📊 Changes **217 files changed** (+10388 additions, -8397 deletions) <details> <summary>View changed files</summary> 📝 `.env.example` (+6 -1) 📝 `CHANGELOG.md` (+0 -54) ➕ `DEPENDENCY_SETUP_COMPLETE.md` (+76 -0) ➕ `ORCA_PROJECT_PLAN.md` (+1162 -0) ➕ `ORCA_REAL_ESTATE_AI_PRD.md` (+520 -0) ➕ `ORCA_REAL_ESTATE_PRD.md` (+686 -0) ➖ `backend/data/readme.txt` (+0 -1) 📝 `backend/open_webui/config.py` (+24 -19) ➖ `backend/open_webui/data/readme.txt` (+0 -1) 📝 `backend/open_webui/env.py` (+3 -7) 📝 `backend/open_webui/functions.py` (+1 -1) 📝 `backend/open_webui/main.py` (+11 -104) 📝 `backend/open_webui/models/channels.py` (+0 -4) 📝 `backend/open_webui/models/chats.py` (+1 -16) 📝 `backend/open_webui/models/files.py` (+0 -11) 📝 `backend/open_webui/models/notes.py` (+8 -61) 📝 `backend/open_webui/models/oauth_sessions.py` (+0 -20) 📝 `backend/open_webui/models/tools.py` (+0 -2) 📝 `backend/open_webui/retrieval/utils.py` (+1 -7) ➖ `backend/open_webui/retrieval/web/ollama.py` (+0 -51) _...and 80 more files_ </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:** - [ ] **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](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/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 to validate 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 clearly 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 - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <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 2026-04-25 12:35:45 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#40187