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

feat(hooks): add console warning | task CU-86c19zx2q #3363

Conversation

FussuChalice
Copy link
Contributor

Description

[FEAT] Add console warning https://app.clickup.com/t/86c19zx2q

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

@rhahao
Copy link
Member

rhahao commented Jan 11, 2025

Task linked: CU-86c19zx2q [FEAT] Add console warning

Copy link

vercel bot commented Jan 11, 2025

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

Name Status Preview Updated (UTC)
organized-app ✅ Ready (Inspect) Visit Preview Jan 12, 2025 5:24pm

Copy link
Contributor

coderabbitai bot commented Jan 11, 2025

Walkthrough

This pull request introduces a new custom React hook useConsoleWarning that logs a warning message when a component is first mounted. The hook is added to the hooks index for easy importing, integrated into the RootLayout component, and includes translation capabilities. Additionally, a new breakpoint variable tablet500Down is added to the PersonsAll component to potentially support future responsive design adjustments.

Changes

File Change Summary
src/hooks/index.ts Added export for useConsoleWarning hook
src/hooks/useConsoleWarning.tsx Created new custom hook that logs translated console warning messages using useEffect and useRef
src/layouts/root_layout/index.tsx Imported and invoked useConsoleWarning hook
src/pages/persons/all_persons/index.tsx Added tablet500Down breakpoint variable from useBreakpoints hook

Possibly related PRs

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@@ -105,6 +106,7 @@ const PersonsAll = () => {
<PersonsSearch />
<Button
variant="secondary"
sx={tablet500Down && { width: '35%' }}
Copy link
Member

Choose a reason for hiding this comment

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

@FussuChalice: not sure if this is intended to be included in this PR, but anyway, this has no effect to the button currently, so it can be removed to avoid confusion later. Thanks.

@FussuChalice FussuChalice requested a review from rhahao January 12, 2025 17:20
Copy link

Please retry analysis of this Pull-Request directly on SonarQube Cloud

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

🧹 Nitpick comments (5)
src/hooks/index.ts (1)

9-9: Maintain alphabetical order of exports

Consider moving the useConsoleWarning export to maintain alphabetical order with other hooks.

 export { default as useAppTranslation } from './useAppTranslation';
 export { default as useBreakpoints } from './useBreakpoints';
+export { default as useConsoleWarning } from './useConsoleWarning';
 export { default as useCurrentUser } from './useCurrentUser';
 export { default as useFirebaseAuth } from './useFirebaseAuth';
 export { default as useGlobal } from './useGlobal';
 export { default as useInternetChecker } from './useInternetChecker';
 export { default as useIntersectionObserver } from './useIntersectionObserver';
 export { default as useUserAutoLogin } from './useUserAutoLogin';
-export { default as useConsoleWarning } from './useConsoleWarning';
src/hooks/useConsoleWarning.tsx (4)

4-29: Add JSDoc documentation for the hook

Consider adding documentation to explain the hook's purpose, usage, and when it should be used.

+/**
+ * A custom hook that displays a styled console warning message on component mount.
+ * Used to show important notices to developers in the browser console.
+ */
 const useConsoleWarning = () => {

10-20: Move style templates outside useEffect

The style templates are static and don't need to be recreated on each effect run. Consider moving them outside the hook as constants.

+const CONSOLE_WARNING_TITLE_STYLE = ` 
+    background: #DD8C2C; 
+    color: #FFFFFF; 
+    font-size: 48px; 
+    font-weight: 700;
+`;
+
+const CONSOLE_WARNING_DESC_STYLE = `
+    font-weight: 500; 
+    font-size: 32px;
+`;

 const useConsoleWarning = () => {
   const { t } = useAppTranslation();
   const warningShownRef = useRef(false);

   useEffect(() => {
-    const consoleWarningTitleStyle = ` 
-        background: #DD8C2C; 
-        color: #FFFFFF; 
-        font-size: 48px; 
-        font-weight: 700;
-    `;
-
-    const consoleWarningDescStyle = `
-        font-weight: 500; 
-        font-size: 32px;
-    `;

     if (!warningShownRef.current) {
-      console.log(`%c${t('tr_consoleWarningTitle')}`, consoleWarningTitleStyle);
-      console.log(`%c${t('tr_consoleWarningDesc')}`, consoleWarningDescStyle);
+      console.log(`%c${t('tr_consoleWarningTitle')}`, CONSOLE_WARNING_TITLE_STYLE);
+      console.log(`%c${t('tr_consoleWarningDesc')}`, CONSOLE_WARNING_DESC_STYLE);

23-24: Consider using console.warn instead of console.log

Since this is a warning message, using console.warn would be more semantically correct and provide better visibility in the console.

-      console.log(`%c${t('tr_consoleWarningTitle')}`, consoleWarningTitleStyle);
-      console.log(`%c${t('tr_consoleWarningDesc')}`, consoleWarningDescStyle);
+      console.warn(`%c${t('tr_consoleWarningTitle')}`, consoleWarningTitleStyle);
+      console.warn(`%c${t('tr_consoleWarningDesc')}`, consoleWarningDescStyle);

5-5: Type-check translation keys

Consider adding type safety for translation keys to prevent runtime errors.

+type ConsoleWarningTranslationKeys = 'tr_consoleWarningTitle' | 'tr_consoleWarningDesc';
+
 const useConsoleWarning = () => {
-  const { t } = useAppTranslation();
+  const { t } = useAppTranslation<ConsoleWarningTranslationKeys>();
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a51b6f4 and e5ac65d.

⛔ Files ignored due to path filters (1)
  • src/locales/en/general.json is excluded by !**/*.json
📒 Files selected for processing (4)
  • src/hooks/index.ts (1 hunks)
  • src/hooks/useConsoleWarning.tsx (1 hunks)
  • src/layouts/root_layout/index.tsx (1 hunks)
  • src/pages/persons/all_persons/index.tsx (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Summary
🔇 Additional comments (2)
src/pages/persons/all_persons/index.tsx (1)

22-22: Remove unused breakpoint variable

The tablet500Down breakpoint is destructured but never used in the component. Consider removing it to avoid confusion.

-  const { desktopUp, tablet500Down } = useBreakpoints();
+  const { desktopUp } = useBreakpoints();
src/layouts/root_layout/index.tsx (1)

32-37: LGTM! Good placement of the console warning hook

The placement of useConsoleWarning in the RootLayout component ensures the warning is shown once when the app starts, which is the appropriate behavior.

@rhahao rhahao merged commit 66406f8 into sws2apps:main Jan 13, 2025
11 checks passed
Copy link

cypress bot commented Jan 13, 2025

organized-app    Run #1933

Run Properties:  status check passed Passed #1933  •  git commit 66406f8643: chore(app): add console warning
Project organized-app
Branch Review main
Run status status check passed Passed #1933
Run duration 00m 05s
Commit git commit 66406f8643: chore(app): add console warning
Committer Max Makaluk
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 1
View all changes introduced in this branch ↗︎

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