QuivrHQ / quivr

Opiniated RAG for integrating GenAI in your apps 🧠 Focus on your product rather than the RAG. Easy integration in existing products with customisation! Any LLM: GPT4, Groq, Llama. Any Vectorstore: PGVector, Faiss. Any Files. Anyway you want.
https://core.quivr.com
Other
36.65k stars 3.58k forks source link

[Improvement UX Chat ] A.0 AAU, I can see the language + the light preferences in the user page #1255

Closed gozineb closed 1 year ago

gozineb commented 1 year ago

Epic

1231

Functional

Remove the two buttons from the navbar: The Language and the light preferences. Move them to the user's page.

Schema

Tech

Tests

Validation Checks

dosubot[bot] commented 1 year ago

🤖

Hello,

Thank you for your suggestion to improve the user experience by adding the language and light preferences to the user page. This is indeed a great idea and can be implemented using the existing LanguageDropDown and DarkModeToggle components.

Here is a simple example of how you can add these components to your user page:

import { LanguageDropDown } from "@/lib/components/NavBar/components/NavItems/components/LanguageDropDown/LanguageDropDown";
import { DarkModeToggle } from "@/lib/components/NavBar/components/NavItems/components/DarkModeToggle/DarkModeToggle";

export const UserPage = (): JSX.Element => {
  return (
    <>
      <h1>User Page</h1>
      <LanguageDropDown />
      <DarkModeToggle />
    </>
  );
};

Please note that this is a simplified example and you might need to adjust it according to your actual project structure and requirements.

As for the current structure of the user page in the Quivr codebase, it is a functional component that uses several hooks and returns a JSX.Element. If the session is null, it redirects to the login page. The returned JSX.Element is a main element with two sections. The first section contains a div that either displays user statistics (if userStats is not null) or a spinner with a fetching message (if userStats is null).

Unfortunately, I couldn't find the current version of the Quivr codebase where this change is to be implemented. Could you please provide more information about this?

Thank you for your contribution to improving Quivr. If you have any other suggestions or need further assistance, feel free to ask.

Best regards, Dosu

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

gozineb commented 1 year ago

Do not close until validated @matthieujacq