Skip to content
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

fix: remove undesired outlines around divs #1316

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

matthieujacq
Copy link
Contributor

@matthieujacq matthieujacq commented Oct 3, 2023

Description

Remove the outline when focusing on divs
#1317

Screenshots of the issue (before)

image

image

@matthieujacq matthieujacq added the area: frontend Related to frontend functionality or under the /frontend directory label Oct 3, 2023
@matthieujacq matthieujacq self-assigned this Oct 3, 2023
@vercel
Copy link

vercel bot commented Oct 3, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview Oct 3, 2023 3:49pm
quivr-strapi ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 3, 2023 3:49pm
quivrapp ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 3, 2023 3:49pm

@matthieujacq matthieujacq temporarily deployed to preview October 3, 2023 15:47 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Oct 3, 2023

Risk Level 2 - /home/runner/work/quivr/quivr/frontend/app/chat/[chatId]/page.tsx

The changes made in the pull request seem to be mostly related to the styling and layout of the components. However, there are a few things that could be improved:

  1. Removal of ChatDialogueArea and ActionsBar: The ChatDialogueArea and ActionsBar components have been removed from the SelectedChatPage component. If these components are necessary for the functionality of the chat page, their removal could cause issues. Please ensure that these components are not required, or if they are, they are being rendered elsewhere.

  2. Removal of getRootProps: The getRootProps function from the useCustomDropzone hook is no longer being spread onto the div element. If this function is providing necessary props for the functionality of the dropzone, its removal could cause issues.

  3. Styling Changes: The changes to the class names on the div elements seem to be mostly related to styling. While these changes are unlikely to cause any major issues, it's worth double checking that they don't unintentionally alter the layout or appearance of the components in a way that wasn't intended.

Here's a suggestion on how to possibly improve the code:

const SelectedChatPage = (): JSX.Element => {
  const { getRootProps } = useCustomDropzone();
  const { shouldDisplayFeedCard } = useKnowledgeToFeedContext();

  return (
    <div
      className={`flex flex-col flex-1 items-center justify-stretch w-full h-[100vh] overflow-hidden ${
        shouldDisplayFeedCard ? \"bg-chat-bg-gray\" : \"bg-white\"
      } dark:bg-black transition-colors ease-out duration-500`}
      data-testid=\"chat-page\"
      {...getRootProps()}
    >
      <div
        className={`flex flex-col flex-1 w-full max-w-5xl h-full dark:shadow-primary/25 overflow-hidden p-2 sm:p-4 md:p-6 lg:p-8`}
      >
        <div className=\"flex flex-1 flex-col overflow-y-auto\">
          <ChatDialogueArea />
        </div>
        <ActionsBar />
      </div>
    </div>
  );
};

export default SelectedChatPage;

This way, you maintain the functionality of the ChatDialogueArea and ActionsBar components, as well as the getRootProps function, while still applying the new styles.


🔧🧹🎨


Powered by Code Review GPT

@matthieujacq matthieujacq merged commit 403cdaa into main Oct 3, 2023
13 checks passed
@matthieujacq matthieujacq deleted the fix/unwanted-outline-on-divs branch October 4, 2023 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: frontend Related to frontend functionality or under the /frontend directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants