Skip to content

fix(tailwind): resolve custom classNames recognition #269

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 1 commit into
base: master
Choose a base branch
from

Conversation

heydoyouknowme0
Copy link
Contributor

No description provided.

Copy link

@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 updates the custom Tailwind class name props in various UI components to use a nested object property called classNames instead of individual props.

  • Replaces multiple props (e.g., scrollAreaClassName, inputClassName, badgeClassName) with a unified classNames object.
  • Updates component implementations in table, scroll-area, inputs, carousels, buttons, search, login, and library pages to support the new API.

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
components/ui/table.tsx Updated component prop interface to use classNames and applied the new keys in the ScrollArea usage.
components/ui/scroll-area.tsx Changed prop interface to use classNames for scrollBar styling and updated its usage.
components/inputs/multi-select.tsx Replaced badgeClassName with classNames for badge styling.
components/inputs/input.tsx Converted inputClassName into classNames for input styling.
components/carousels/gallery.tsx Updated itemClassName prop to classNames for item styling.
components/buttons/bouncy-arrow.tsx Modified arrowClassName to classNames for arrow styling.
app/[locale]/search/search.tsx Adapted Input and BouncyArrowButton usage to the new classNames API.
app/[locale]/login/login.tsx Changed Input component usage from inputClassName to classNames.
app/[locale]/institute/sections/library/collection-and-resources/page.tsx Updated Table usage but passed classNames with the wrong key.

Copy link

@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 updates various UI components to use a consolidated "classNames" prop instead of multiple discrete class name props, specifically for improved Tailwind custom class recognition.

  • Updated Table, ScrollArea, Input, MultiSelect, GalleryCarousel, and BouncyArrowButton components to accept a "classNames" object with related sub-keys.
  • Modified app pages (search, login, library) to use the new "classNames" prop structure.

Reviewed Changes

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

Show a summary per file
File Description
components/ui/table.tsx Replaced scrollAreaClassName with classNames.scrollArea and added classNames.scrollBar for the ScrollBar.
components/ui/scroll-area.tsx Replaced scrollBarClassName with classNames.scrollBar.
components/inputs/multi-select.tsx Replaced badgeClassName with classNames.badge.
components/inputs/input.tsx Replaced inputClassName with classNames.input in component props and rendering.
components/carousels/gallery.tsx Replaced itemClassName with classNames.item in the GalleryCarousel component.
components/buttons/bouncy-arrow.tsx Replaced arrowClassName with classNames.arrow.
app/[locale]/search/search.tsx Updated Input and BouncyArrowButton props to use the new classNames structure.
app/[locale]/login/login.tsx Updated Input props to use classNames.input.
app/[locale]/institute/sections/library/collection-and-resources/page.tsx Updated Table props to use classNames.scrollArea.

@heydoyouknowme0
Copy link
Contributor Author

I think this is good to merge right?

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