You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason will be displayed to describe this comment to others. Learn more.
Bug: Flex Direction Change Breaks Vertical Layouts
Commenting out flex-direction(column) for the .flex class changes its default behavior from column to row. This breaks existing layouts across the application that depend on .flex for vertical stacking.
The reason will be displayed to describe this comment to others. Learn more.
Bug: Development Code Leaks to Production
A debug paragraph element <p>yolo</p> was accidentally committed to the Users and Permissions page, making temporary development code visible in production.
The reason will be displayed to describe this comment to others. Learn more.
Bug: Global Paragraph Color Override Bug
The global p { color: var(--text-primary) !important; } rule forces all paragraph text to be red in light mode (yellow in dark mode). The !important flag overrides existing styles, breaking the design system and semantic text colors across the application. This appears to be debug code.
The reason will be displayed to describe this comment to others. Learn more.
Bug: Overflow Button Styling Conflict
Adding btn btn-secondary classes to the overflow button div conflicts with its existing inline styles (e.g., backgroundColor, borderRadius, height, width). This changes the visual appearance of the tabs overflow menu and is semantically incorrect for a div element.
The reason will be displayed to describe this comment to others. Learn more.
Bug: Tailwind Base Styles Duplicated, Variables Undefined
The @tailwind base directive is included twice: once directly and again via the tailwind.css import. This duplicates Tailwind's base styles, increasing bundle size and potentially causing CSS specificity issues. Additionally, these Tailwind imports occur before the variables file, meaning custom SCSS variables are not defined when Tailwind's base styles are processed.
The reason will be displayed to describe this comment to others. Learn more.
Bug: Red Feature Names in Dark Mode
The dark:text-red-500 class was accidentally committed, causing feature names to appear red in dark mode. This appears to be test code from the Tailwind POC and is not intended for production.
The reason will be displayed to describe this comment to others. Learn more.
Bug: Red Text Bug in Tailwind Config
The default text color in tailwind.config.js is set to #FF0000 (red), which appears to be debug code. This makes all default text red across the application, breaking the visual design.
@Zaimwa9
Should we consider adding a prefix on tailwind classes in order to avoid conflicts ?
like tw-*, then we can remove it after the full migration. (just an idea...)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
featureNew feature or requestfront-endIssue related to the React Front End Dashboard
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
Please describe.
How did you test this code?
Please describe.
Note
Add Tailwind CSS and Autoprefixer via PostCSS, wire into webpack, and apply initial Tailwind-based style/class updates.
tailwindcss,autoprefixer, andeslint-plugin-tailwindcss; createpostcss.config.js.tailwind.config.jswith custom theme (colors, fonts, radii, spacing, dark mode via class, preflight disabled).postcss-loaderforcss/scssinlocal,prod, and Django builds.web/styles/tailwind.cssand reference inweb/main.jsandstyles.scss..tabsbase styles.components/_input.scsscommented out.d-flex→flex, addbtn btn-secondary,dark:text-red-500).FeatureAnalytics.container.tsx,Tabs.tsx,OrganisationNavbar.tsx,UsersAndPermissionsPage.tsx.Written by Cursor Bugbot for commit 680d781. This will update automatically on new commits. Configure here.