Skip to content

feat/redesign-and-improvements #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

huhn511
Copy link
Collaborator

@huhn511 huhn511 commented May 25, 2025

Overview

This PR introduces several improvements to the frontend application, focusing on customization options and document handling. The main changes include environment-based configuration, enhanced document interactions, and visual refinements.

Changes

Environment-Based Settings Configuration

  • Added support for loading application settings from environment variables
  • Default fallbacks are provided when environment variables are not set
  • Settings can now be configured through .env files using the VITE_ prefix
  • Documented the configuration options in the shared folder README

Document Experience Improvements

  • Added document mock endpoint for improved development and testing
  • Refactored documentItem component for better user experience
  • Enhanced UI interactions and visual feedback for document operations

Visual Updates

  • Updated chat icon for better visual consistency
  • Added new color options for theming
  • Implemented customizable bot settings (name, appearance)

How to Test

  1. Create a .env file with custom settings:
    VITE_BOT_NAME=Custom Bot
    VITE_UI_THEME_DEFAULT=dark
    
  2. Verify settings are applied correctly in the UI
  3. Test document interaction with the new mock endpoint
  4. Confirm theme switching works with customized options

Screenshots

tbd

@huhn511 huhn511 marked this pull request as ready for review May 26, 2025 15:40
@huhn511 huhn511 requested a review from Copilot May 31, 2025 12:41
Copilot

This comment was marked as outdated.

huhn511 and others added 5 commits June 16, 2025 12:52
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- Moved i18n access to function call time instead of store definition
time - Added error handling with a fallback message - Called
getInitialMessage() when actually needed in initiateConversation()
@huhn511 huhn511 requested a review from Copilot June 20, 2025 11:03
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR refactors configuration management and improves the document and chat interactions across the frontend and admin applications. Key changes include adding environment-based settings and aliases, enhancing document upload and interaction flows, and updating theming and visual components.

Reviewed Changes

Copilot reviewed 22 out of 23 changed files in this pull request and generated no comments.

Show a summary per file
File Description
frontend/tsconfig.base.json Added new alias entries for shared settings and theme store
frontend/tailwind.config.js Updated theming configuration and color options
frontend/libs/shared/ui/ThemeToggle.vue Introduced a theme toggle component supporting light/dark modes
frontend/libs/shared/ui/NavigationContainer.vue Updated navigation header to use dynamic logo and theme styling
frontend/libs/shared/store/theme.store.ts Added theme persistence and apply functions via Pinia store
frontend/libs/shared/settings.ts Provided environment variable support and fallback defaults
Others (chat-app, admin-app, docs, etc.) Improved document handling, chat messaging, and UI customization
Comments suppressed due to low confidence (3)

frontend/libs/admin-app/data-access/+state/documents.store.ts:11

  • The store id is set to "chat" which could be confusing as this store handles document-related state. Consider renaming the store id to "documents" for clarity and to avoid potential collisions.
export const useDocumentsStore = defineStore("chat", () => {

frontend/libs/shared/ui/NavigationContainer.vue:14

  • The property 'themeStore.isDarkMode' is used but not defined in the theme store. Consider replacing it with a computed check such as 'themeStore.currentTheme === "dark"' to ensure proper functionality.
  <div :class="`${themeStore.isDarkMode ? 'bg-dark-primary' : 'bg-light-primary'} flex p-4`">

frontend/libs/chat-app/ui/ChatBubble.vue:63

  • The v-for loop iterates over 'anchorIds', but this variable is not defined; it should reference 'props.anchorIds'. Updating this will ensure the correct data is used for rendering document jump anchors.
        >

Copy link
Member

@a-klos a-klos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

friendly reminder^^:

  • indentation
  • dark mode default
  • something else that i most probably forgot :D

file and sitemap loader still work. confluence not tested... its not configured in the uni deployment ^^

### UI Customization
- VITE_BOT_NAME = The AI assistant's display name (default: "Knowledge Agent")
- VITE_UI_LOGO_PATH = Path to the main navigation logo (default: "/assets/navigation-logo.svg")
- VITE_UI_THEME_DEFAULT = Default theme when user first visits (default: "light")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: dark might be nice ^^

ui: {
logoPath: "/assets/navigation-logo.svg",
theme: {
default: "light",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought: i guess here or so

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants