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

NoMongo: Fix Stylesheet in Anticipation of Dark Mode [PR-5] #3750

Merged

Conversation

hustlernik
Copy link
Contributor

@hustlernik hustlernik commented Feb 25, 2025

What kind of change does this PR introduce?

CSS Refactor

Issue Number:

Fixes #3296

Does this PR introduce a breaking change?

Checklist

CodeRabbit AI Review

  • I have reviewed and addressed all critical issues flagged by CodeRabbit AI
  • I have implemented or provided justification for each non-critical suggestion
  • I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

  • I have written tests for all new changes/features
  • I have verified that test coverage meets or exceeds 95%
  • I have run the test suite locally and all tests pass

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Style
    • Updated numerous components to leverage a centralized styling resource, ensuring more consistent visual presentation across the application.
  • Chore
    • Removed obsolete local style files, streamlining and cleaning up the overall CSS structure.

Copy link
Contributor

coderabbitai bot commented Feb 25, 2025

Walkthrough

This PR updates numerous component files to import CSS from a centralized global stylesheet (app-fixed.module.css) instead of various local CSS modules. The changes involve updating the import paths in over 30 .tsx components and refactoring the global CSS file, including moving the @keyframes zoomIn declaration and adjusting several class properties. Additionally, several obsolete CSS module files have been removed to streamline styling across the application.

Changes

File(s) Change Summary
src/components/.../*.tsx (e.g., AddOnRegister, AddOnStore, MainContent, etc.) Updated import statements to reference the centralized app-fixed.module.css instead of local CSS modules (app.module.css, ./*.module.css).
src/style/app.module.css Refactored CSS: moved @keyframes zoomIn outside a scoped class, updated .buttonList, .entrytoggle, and .entryaction classes, and removed commented sections.
src/components/.../*.module.css (e.g., DynamicDropDown, InfiniteScrollLoader, OrgSettings/General/*) Removed obsolete CSS module files along with their associated classes and keyframes.

Possibly related PRs

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes

Poem

I’m a bunny with a joyful cheer,
Hoping through code with a spring so clear,
Local styles hop away, making room anew,
As global CSS shows its debut.
With a twitch of my nose and a gentle leap,
I celebrate clean code, crisp and deep!


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dba366c and e21b50c.

📒 Files selected for processing (1)
  • src/components/EventManagement/EventRegistrant/EventRegistrants.spec.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/EventManagement/EventRegistrant/EventRegistrants.spec.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test Application

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🔭 Outside diff range comments (1)
src/style/app.module.css (1)

4480-4517: 🛠️ Refactor suggestion

Ensure animation definitions are consistent.

There are duplicate @keyframes definitions for zoomIn (one at line 4754 and another at line 4480). Consider consolidating these to avoid potential conflicts in animation behavior.

- @-webkit-keyframes zoomIn {
-   0% {
-     opacity: 0;
-     -webkit-transform: scale(0.5);
-     transform: scale(0.5);
-   }
-   100% {
-     opacity: 1;
-     -webkit-transform: scale(1);
-     transform: scale(1);
-   }
- }
-
- @keyframes zoomIn {
-   0% {
-     opacity: 0;
-     -webkit-transform: scale(0.5);
-     transform: scale(0.5);
-   }
-   100% {
-     opacity: 1;
-     -webkit-transform: scale(1);
-     transform: scale(1);
-   }
- }

Keep only one set of these keyframes definitions to maintain consistency and reduce file size.

🧹 Nitpick comments (3)
src/style/app.module.css (3)

4768-4770: Ensure specificity without !important if possible.

The .buttonList class now uses !important to enforce the background color. While this ensures the style is applied consistently regardless of specificity conflicts, using !important should generally be avoided for maintainability.

When preparing for dark mode, consider using CSS custom properties with proper selector specificity instead.

- .buttonList {
-   background-color: var(--buttonList-bg) !important;
- }
+ .buttonList {
+   background-color: var(--buttonList-bg);
+ }

Then use more specific selectors in your theme definitions if needed to override the styles.


6241-6315: Consider using CSS variables for color definitions in component-specific styles.

In component-specific sections like the YearlyEventCalender styles, many colors are hardcoded. As part of the dark mode preparation, consider converting these hardcoded colors to use the CSS variables defined in the :root.

.day__selected {
-  background-color: var(--blue-primary);
+  background-color: var(--calendar-selected-day-bg, var(--blue-primary));
  color: var(--grey-dark);
}

.day__today {
-  background-color: var(--light-neon-green);
+  background-color: var(--calendar-today-bg, var(--light-neon-green));
  font-weight: 700;
  text-decoration: underline;
-  color: var(--light-green);
+  color: var(--calendar-today-text, var(--light-green));
}

4767-4791: Ensure AddOnEntry component styling is properly scoped.

The added styles for .entrytoggle and .entryaction appear to be specifically for the AddOnEntry component (based on the comment on line 4771). To better organize styles and prevent potential conflicts, consider moving component-specific styles to a separate CSS module file or ensuring proper namespacing.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e7179c4 and 3fdedd0.

📒 Files selected for processing (63)
  • src/components/AddOn/core/AddOnRegister/AddOnRegister.tsx (1 hunks)
  • src/components/AddOn/core/AddOnStore/AddOnStore.tsx (1 hunks)
  • src/components/AddOn/support/components/MainContent/MainContent.tsx (1 hunks)
  • src/components/AddOn/support/components/SidePanel/SidePanel.tsx (1 hunks)
  • src/components/AddPeopleToTag/AddPeopleToTag.tsx (1 hunks)
  • src/components/Advertisements/Advertisements.tsx (1 hunks)
  • src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx (1 hunks)
  • src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.tsx (1 hunks)
  • src/components/AgendaItems/AgendaItemsContainer.tsx (1 hunks)
  • src/components/AgendaItems/Delete/AgendaItemsDeleteModal.tsx (1 hunks)
  • src/components/AgendaItems/Preview/AgendaItemsPreviewModal.tsx (1 hunks)
  • src/components/ContriStats/ContriStats.tsx (1 hunks)
  • src/components/CurrentHourIndicator/CurrentHourIndicator.tsx (1 hunks)
  • src/components/DynamicDropDown/DynamicDropDown.module.css (0 hunks)
  • src/components/DynamicDropDown/DynamicDropDown.tsx (1 hunks)
  • src/components/EventCalender/Header/EventHeader.tsx (1 hunks)
  • src/components/EventCalender/Monthly/EventCalender.tsx (1 hunks)
  • src/components/EventCalender/Yearly/YearlyEventCalender.tsx (1 hunks)
  • src/components/EventDashboardScreen/EventDashboardScreen.tsx (1 hunks)
  • src/components/EventListCard/EventListCard.tsx (1 hunks)
  • src/components/EventListCard/Modal/Delete/EventListCardDeleteModal.tsx (1 hunks)
  • src/components/EventListCard/Modal/Preview/EventListCardPreviewModal.tsx (1 hunks)
  • src/components/EventListCard/Modal/Update/EventListCardUpdateModal.tsx (1 hunks)
  • src/components/EventManagement/Dashboard/EventDashboard.tsx (1 hunks)
  • src/components/EventManagement/EventAgendaItems/EventAgendaItems.tsx (1 hunks)
  • src/components/EventManagement/EventAttendance/Attendance/EventAttendance.tsx (1 hunks)
  • src/components/EventManagement/EventAttendance/Statistics/EventStatistics.tsx (1 hunks)
  • src/components/EventManagement/EventRegistrant/EventRegistrants.tsx (1 hunks)
  • src/components/EventRegistrantsModal/EventRegistrantsWrapper.tsx (1 hunks)
  • src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.tsx (1 hunks)
  • src/components/EventStats/EventStatsWrapper.tsx (1 hunks)
  • src/components/EventStats/Statistics/AverageRating/AverageRating.tsx (1 hunks)
  • src/components/GroupChatDetails/GroupChatDetails.tsx (1 hunks)
  • src/components/HolidayCards/HolidayCard.tsx (1 hunks)
  • src/components/InfiniteScrollLoader/InfiniteScrollLoader.module.css (0 hunks)
  • src/components/InfiniteScrollLoader/InfiniteScrollLoader.tsx (1 hunks)
  • src/components/LeftDrawer/LeftDrawer.tsx (1 hunks)
  • src/components/OrgListCard/OrgListCard.tsx (1 hunks)
  • src/components/OrgPeopleListCard/OrgPeopleListCard.tsx (1 hunks)
  • src/components/OrgPostCard/DeleteModal/DeletePostModal.tsx (1 hunks)
  • src/components/OrgPostCard/OrgPostCard.tsx (1 hunks)
  • src/components/OrgSettings/ActionItemCategories/Modal/CategoryModal.tsx (1 hunks)
  • src/components/OrgSettings/ActionItemCategories/OrgActionItemCategories.tsx (1 hunks)
  • src/components/OrgSettings/AgendaItemCategories/Create/AgendaCategoryCreateModal.tsx (1 hunks)
  • src/components/OrgSettings/AgendaItemCategories/Delete/AgendaCategoryDeleteModal.tsx (1 hunks)
  • src/components/OrgSettings/AgendaItemCategories/OrganizationAgendaCategory.tsx (1 hunks)
  • src/components/OrgSettings/AgendaItemCategories/Preview/AgendaCategoryPreviewModal.tsx (1 hunks)
  • src/components/OrgSettings/AgendaItemCategories/Update/AgendaCategoryUpdateModal.tsx (1 hunks)
  • src/components/OrgSettings/General/DeleteOrg/DeleteOrg.module.css (0 hunks)
  • src/components/OrgSettings/General/DeleteOrg/DeleteOrg.tsx (1 hunks)
  • src/components/OrgSettings/General/OrgProfileFieldSettings/OrgProfileFieldSettings.module.css (0 hunks)
  • src/components/OrgSettings/General/OrgProfileFieldSettings/OrgProfileFieldSettings.tsx (1 hunks)
  • src/components/OrgSettings/General/OrgUpdate/OrgUpdate.module.css (0 hunks)
  • src/components/OrgSettings/General/OrgUpdate/OrgUpdate.tsx (1 hunks)
  • src/components/OrganizationCard/OrganizationCard.tsx (1 hunks)
  • src/components/OrganizationCardStart/OrganizationCardStart.tsx (1 hunks)
  • src/components/OrganizationDashCards/CardItem/CardItem.tsx (1 hunks)
  • src/components/OrganizationDashCards/CardItem/Loader/CardItemLoading.tsx (1 hunks)
  • src/components/OrganizationDashCards/DashboardCard.tsx (1 hunks)
  • src/components/OrganizationDashCards/Loader/DashboardCardLoading.tsx (1 hunks)
  • src/components/OrganizationScreen/OrganizationScreen.tsx (1 hunks)
  • src/components/UserPortal/OrganizationCard/OrganizationCard.tsx (1 hunks)
  • src/style/app.module.css (1 hunks)
💤 Files with no reviewable changes (5)
  • src/components/DynamicDropDown/DynamicDropDown.module.css
  • src/components/InfiniteScrollLoader/InfiniteScrollLoader.module.css
  • src/components/OrgSettings/General/DeleteOrg/DeleteOrg.module.css
  • src/components/OrgSettings/General/OrgProfileFieldSettings/OrgProfileFieldSettings.module.css
  • src/components/OrgSettings/General/OrgUpdate/OrgUpdate.module.css
✅ Files skipped from review due to trivial changes (57)
  • src/components/OrgPeopleListCard/OrgPeopleListCard.tsx
  • src/components/EventDashboardScreen/EventDashboardScreen.tsx
  • src/components/LeftDrawer/LeftDrawer.tsx
  • src/components/OrganizationDashCards/CardItem/CardItem.tsx
  • src/components/GroupChatDetails/GroupChatDetails.tsx
  • src/components/EventManagement/Dashboard/EventDashboard.tsx
  • src/components/UserPortal/OrganizationCard/OrganizationCard.tsx
  • src/components/AddOn/support/components/SidePanel/SidePanel.tsx
  • src/components/HolidayCards/HolidayCard.tsx
  • src/components/EventListCard/Modal/Update/EventListCardUpdateModal.tsx
  • src/components/OrganizationDashCards/DashboardCard.tsx
  • src/components/EventManagement/EventAttendance/Statistics/EventStatistics.tsx
  • src/components/EventStats/EventStatsWrapper.tsx
  • src/components/EventCalender/Monthly/EventCalender.tsx
  • src/components/OrgSettings/General/DeleteOrg/DeleteOrg.tsx
  • src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.tsx
  • src/components/OrgSettings/General/OrgProfileFieldSettings/OrgProfileFieldSettings.tsx
  • src/components/EventManagement/EventRegistrant/EventRegistrants.tsx
  • src/components/OrgSettings/AgendaItemCategories/Update/AgendaCategoryUpdateModal.tsx
  • src/components/OrgSettings/AgendaItemCategories/OrganizationAgendaCategory.tsx
  • src/components/EventListCard/Modal/Delete/EventListCardDeleteModal.tsx
  • src/components/CurrentHourIndicator/CurrentHourIndicator.tsx
  • src/components/OrganizationDashCards/Loader/DashboardCardLoading.tsx
  • src/components/AgendaItems/AgendaItemsContainer.tsx
  • src/components/EventManagement/EventAgendaItems/EventAgendaItems.tsx
  • src/components/OrganizationCard/OrganizationCard.tsx
  • src/components/EventListCard/EventListCard.tsx
  • src/components/OrgSettings/General/OrgUpdate/OrgUpdate.tsx
  • src/components/InfiniteScrollLoader/InfiniteScrollLoader.tsx
  • src/components/OrgPostCard/OrgPostCard.tsx
  • src/components/OrgSettings/AgendaItemCategories/Delete/AgendaCategoryDeleteModal.tsx
  • src/components/AddPeopleToTag/AddPeopleToTag.tsx
  • src/components/ContriStats/ContriStats.tsx
  • src/components/AgendaItems/Delete/AgendaItemsDeleteModal.tsx
  • src/components/EventCalender/Yearly/YearlyEventCalender.tsx
  • src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.tsx
  • src/components/AddOn/core/AddOnRegister/AddOnRegister.tsx
  • src/components/OrgSettings/ActionItemCategories/Modal/CategoryModal.tsx
  • src/components/OrgSettings/ActionItemCategories/OrgActionItemCategories.tsx
  • src/components/AddOn/support/components/MainContent/MainContent.tsx
  • src/components/OrgSettings/AgendaItemCategories/Preview/AgendaCategoryPreviewModal.tsx
  • src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.tsx
  • src/components/EventManagement/EventAttendance/Attendance/EventAttendance.tsx
  • src/components/EventRegistrantsModal/EventRegistrantsWrapper.tsx
  • src/components/OrganizationScreen/OrganizationScreen.tsx
  • src/components/OrganizationDashCards/CardItem/Loader/CardItemLoading.tsx
  • src/components/OrgPostCard/DeleteModal/DeletePostModal.tsx
  • src/components/EventListCard/Modal/Preview/EventListCardPreviewModal.tsx
  • src/components/DynamicDropDown/DynamicDropDown.tsx
  • src/components/OrgListCard/OrgListCard.tsx
  • src/components/OrganizationCardStart/OrganizationCardStart.tsx
  • src/components/AddOn/core/AddOnStore/AddOnStore.tsx
  • src/components/Advertisements/Advertisements.tsx
  • src/components/OrgSettings/AgendaItemCategories/Create/AgendaCategoryCreateModal.tsx
  • src/components/EventCalender/Header/EventHeader.tsx
  • src/components/AgendaItems/Preview/AgendaItemsPreviewModal.tsx
  • src/components/EventStats/Statistics/AverageRating/AverageRating.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test Application
🔇 Additional comments (7)
src/style/app.module.css (7)

4754-4765: Animation extracted for reusability across components.

The @keyframes zoomIn animation has been correctly extracted from being nested inside the .rightCard class to become a global animation definition. This is a good practice as it allows the animation to be reused by multiple components.


4773-4776: LGTM!

The new .entrytoggle class provides consistent margin and width styling for toggle elements, which will help standardize UI components.


4778-4784: Good encapsulation of display properties.

The .entryaction class properly encapsulates display and alignment properties, which helps maintain consistency for action elements. The use of !important for the display property ensures the element renders correctly regardless of other styles.


1-36: Well-documented CSS methodology.

The comments at the beginning of the file excellently document the CSS methodology used in the project. This provides clear guidance for maintaining consistency across component styles and explains the rationale behind the global classes approach. This type of documentation is particularly valuable when preparing for theme changes like dark mode implementation.


38-378: Thorough CSS variables definition supporting theme switching.

The extensive CSS variables defined in the :root selector provide a solid foundation for implementing dark mode. These variables cover colors, spacing, sizing, and other design elements, making it easier to create alternate themes by simply overriding these variables in a theme-specific selector.


4130-4131: Animation usage aligned with new keyframes definition.

The .talawa_logo class references the newly extracted zoomIn animation, demonstrating the benefit of having the animation defined globally for reuse.


38-113:

❓ Verification inconclusive

Verify color contrast ratios for dark mode accessibility.

When implementing dark mode, ensure that the color combinations maintain sufficient contrast ratios for accessibility. Particularly, check text/background combinations using the variables like --grey-light, --grey-dark, --blue-primary, etc.


🌐 Web query:

What should be the minimum color contrast ratio for WCAG AA compliance?

💡 Result:

The minimum color contrast ratio required for WCAG AA compliance is 4.5:1 for normal-sized text and 3:1 for large text (defined as 18pt/24px or larger, or 14pt/19px bold)[1][2][3][5][8]. These standards ensure readability for users with visual impairments like low vision or color blindness.

Key Requirements

  • Normal Text:
    4.5:1 contrast ratio applies to most body text, subtext, and images containing text smaller than 18pt[4][6].

  • Large Text:
    3:1 ratio is sufficient for headers or text sized ≥18pt (24px) or ≥14pt bold (19px)[3][7][8].

Exceptions

  • Logos/brand names[9], purely decorative elements[5], and inactive UI components[9] are exempt.
  • Text over images or complex backgrounds may require manual verification[3].

Enhanced Standards (WCAG AAA)

For stricter compliance:

  • Normal text requires a 7:1 ratio
  • Large text needs 4.5:1[6][7].

Tools like WebAIM’s Contrast Checker[7] or ADA Site Compliance’s tool[4] can validate ratios automatically. Designers should prioritize these guidelines to improve accessibility for over 300 million people globally with moderate-to-severe vision loss[2][6].

Citations:


Dark Mode Accessibility: Verify Color Contrast Ratios

Please ensure that the dark mode color palette adheres to WCAG AA guidelines. In particular, verify that text and background combinations using variables such as --grey-light, --grey-dark, --blue-primary, etc., achieve at least a 4.5:1 contrast ratio for normal text and 3:1 for large text (≥18pt/24px normal or ≥14pt/19px bold). Consider using tools like WebAIM’s Contrast Checker to validate these ratios across all affected UI elements.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 25, 2025
@hustlernik
Copy link
Contributor Author

hustlernik commented Feb 25, 2025

@palisadoes

  1. This will require one more PR to complete the issue, approx. 20-25 files are left.
  2. In final PR I will change app-fixed.module.css to app.module.css, and prev. app.module.css to app-legacy.module.css.
  3. We will keep app-legacy.module.css for some time before removing it ,this is done because I might have missed some classes to put on place, since I was not able to check all components and screen while refactoring because they were broken.
  4. When are we going to implement dark mode? Do we have some UI designs or color scheme for Dark Mode.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 25, 2025
Copy link

codecov bot commented Feb 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.05%. Comparing base (e7179c4) to head (e21b50c).
Report is 1 commits behind head on develop-postgres.

Additional details and impacted files
@@                Coverage Diff                @@
##           develop-postgres    #3750   +/-   ##
=================================================
  Coverage             86.05%   86.05%           
=================================================
  Files                   371      371           
  Lines                  9139     9139           
  Branches               1925     1925           
=================================================
  Hits                   7865     7865           
  Misses                  909      909           
  Partials                365      365           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@hustlernik
Copy link
Contributor Author

@palisadoes PTAL.

@palisadoes palisadoes merged commit 7ce2718 into PalisadoesFoundation:develop-postgres Feb 25, 2025
19 checks passed
@hustlernik
Copy link
Contributor Author

@palisadoes

  1. This will require one more PR to complete the issue, approx. 20-25 files are left.
  2. In final PR I will change app-fixed.module.css to app.module.css, and prev. app.module.css to app-legacy.module.css.
  3. We will keep app-legacy.module.css for some time before removing it ,this is done because I might have missed some classes to put on place, since I was not able to check all components and screen while refactoring because they were broken.
  4. When are we going to implement dark mode? Do we have some UI designs or color scheme for Dark Mode.

.

@palisadoes
Copy link
Contributor

  1. Propose a color scheme.
  2. The existing design is roughly based on Gmail.
  3. You can use Gmail dark mode as a guide.

@palisadoes
Copy link
Contributor

Dark mode whenever you are ready

@hustlernik
Copy link
Contributor Author

Dark mode whenever you are ready

Working on it. I will complete these two issues on priority #3560 and #3552. After that, I will take this on priority.

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

Successfully merging this pull request may close these issues.

2 participants