-
Notifications
You must be signed in to change notification settings - Fork 47
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
change position of 'Delete this plan' button #3322
change position of 'Delete this plan' button #3322
Conversation
WalkthroughThe pull request introduces modifications to the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure. 🔧 eslint
apps/web/lib/features/user-profile-plans.tsxOops! Something went wrong! :( ESLint: 8.46.0 ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct. The config "next/core-web-vitals" was referenced from the config file in "/apps/web/.eslintrc.json". If you still have problems, please stop by https://eslint.org/chat/help to chat with the team. 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (1)
apps/web/lib/features/user-profile-plans.tsx (1)
187-246
: Improve confirmation popup implementationThe delete button and confirmation popup implementation has a few areas for improvement:
- The empty fragment (
<></>
) in the else condition is unnecessary- The inline comment
//button open popup
is redundant- Consider extracting the delete button and popup into a separate component for better maintainability
Apply these changes:
- {canSeeActivity ? ( - <div className="flex justify-end"> - <AlertPopup + {canSeeActivity && todayPlan[0] && ( + <div className="flex justify-end"> + <AlertPopup open={popupOpen} buttonOpen={ - //button open popup <Button onClick={() => { setPopupOpen((prev) => !prev); }} variant="outline" className="px-4 py-2 text-sm font-medium text-red-600 border border-red-600 rounded-md bg-light--theme-light dark:!bg-dark--theme-light" > {t('common.plan.DELETE_THIS_PLAN')} </Button> } > - </AlertPopup> - </div> - ) : ( - <></> - )} + </AlertPopup> + </div> + )}🧰 Tools
🪛 Biome
[error] 188-245: Avoid using unnecessary Fragment.
A fragment is redundant if it contains only one child, or if it is the child of a html element, and is not a keyed fragment.
Unsafe fix: Remove the Fragment(lint/complexity/noUselessFragments)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
apps/web/lib/features/user-profile-plans.tsx
(6 hunks)
🧰 Additional context used
🪛 Biome
apps/web/lib/features/user-profile-plans.tsx
[error] 188-245: Avoid using unnecessary Fragment.
A fragment is redundant if it contains only one child, or if it is the child of a html element, and is not a keyed fragment.
Unsafe fix: Remove the Fragment
(lint/complexity/noUselessFragments)
🔇 Additional comments (2)
apps/web/lib/features/user-profile-plans.tsx (2)
61-70
: LGTM: Hook usage is properly implemented
The useDailyPlan
hook destructuring now includes deleteDailyPlan
and deleteDailyPlanLoading
, which aligns with the PR objective of managing plan deletion functionality.
290-290
: Verify dependency array in useEffect
The useEffect
dependency array in AllPlans
component now depends on todayPlan
instead of filteredPlans.current
. This is correct as todayPlan
is the source of truth for today's plans.
Also applies to: 305-305
if (requirePlan) { | ||
localStorage.removeItem( | ||
DAILY_PLAN_SUGGESTION_MODAL_DATE | ||
); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider error handling for localStorage operations
The localStorage operation during plan deletion should be wrapped in a try-catch block as it can throw errors in certain browser conditions (e.g., private browsing mode).
Apply this change:
if (requirePlan) {
+ try {
localStorage.removeItem(
DAILY_PLAN_SUGGESTION_MODAL_DATE
);
+ } catch (error) {
+ console.error('Failed to remove from localStorage:', error);
+ }
}
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
if (requirePlan) { | |
localStorage.removeItem( | |
DAILY_PLAN_SUGGESTION_MODAL_DATE | |
); | |
} | |
if (requirePlan) { | |
try { | |
localStorage.removeItem( | |
DAILY_PLAN_SUGGESTION_MODAL_DATE | |
); | |
} catch (error) { | |
console.error('Failed to remove from localStorage:', error); | |
} | |
} |
disabled={deleteDailyPlanLoading} | ||
onClick={async () => { | ||
try { | ||
if (requirePlan) { | ||
localStorage.removeItem( | ||
DAILY_PLAN_SUGGESTION_MODAL_DATE | ||
); | ||
} | ||
todayPlan[0].id && | ||
(await deleteDailyPlan(todayPlan[0].id)); | ||
} catch (error) { | ||
console.error(error); | ||
} finally { | ||
setPopupOpen(false); | ||
} | ||
}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Add user feedback for deletion errors
The error handling during plan deletion only logs to console. Consider showing a user-friendly error message when deletion fails.
Consider adding a toast notification or error message in the UI:
onClick={async () => {
try {
if (requirePlan) {
localStorage.removeItem(
DAILY_PLAN_SUGGESTION_MODAL_DATE
);
}
todayPlan[0].id &&
(await deleteDailyPlan(todayPlan[0].id));
} catch (error) {
console.error(error);
+ // Assuming you have a toast notification system
+ showErrorToast(t('common.errors.FAILED_TO_DELETE_PLAN'));
} finally {
setPopupOpen(false);
}
}}
Committable suggestion skipped: line range outside the PR's diff.
Description
Fix #3127
Type of Change
Checklist
Previous screenshots
Current screenshots
Summary by CodeRabbit
New Features
Improvements