[WEB-5781]chore: removed info banner for preferences
Description
This update removes the redundant info banner at profile settings.
Type of Change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Feature (non-breaking change which adds functionality)
- [x] Improvement (change that would cause existing functionality to not work as expected)
- [ ] Code refactoring
- [ ] Performance improvements
- [ ] Documentation update
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit
- Refactor
- Simplified the profile form interface by removing the informational panel previously displayed on the page.
✏️ Tip: You can customize this high-level summary in your review settings.
Walkthrough
The profile form component was streamlined by removing Next.js routing dependencies (Link, useParams), associated UI elements (InfoIcon), utility functions (getButtonStyling, cn), and a preferences navigation block. Explicit early returns were added after successful profile picture deletion and profile update operations to clarify control flow.
Changes
| Cohort / File(s) | Summary |
|---|---|
Profile Form Simplification apps/web/core/components/profile/form.tsx |
Removed Next.js routing imports (Link, useParams) and InfoIcon; eliminated preferences navigation UI block; removed getButtonStyling and cn utility imports; added explicit early returns after profile picture deletion and profile update success flows |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~8 minutes
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly and specifically describes the main change: removing an info banner for preferences from the profile form component. |
| Description check | ✅ Passed | The description covers the main change and includes a type classification, but lacks screenshots, test scenarios, and references that are part of the template. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✨ Finishing touches
- [ ] 📝 Generate docstrings
🧪 Generate unit tests (beta)
- [ ] Create PR with unit tests
- [ ] Post copyable unit tests in a comment
- [ ] Commit unit tests in branch
chore/profile-form
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands and usage tips.