-
Notifications
You must be signed in to change notification settings - Fork 537
Remove advancedEnabled field from Account interface #7118
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
Remove advancedEnabled field from Account interface #7118
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
WalkthroughThe changes remove the advancedEnabled property from the Account type definition and eliminate its usage in a related stub function. No other type or logic modifications were made, and no changes occurred to exported function signatures. Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
⏰ Context from checks skipped due to timeout of 90000ms (6)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7118 +/- ##
=======================================
Coverage 55.59% 55.59%
=======================================
Files 901 901
Lines 58121 58121
Branches 4068 4068
=======================================
Hits 32315 32315
Misses 25701 25701
Partials 105 105
🚀 New features to boost your workflow:
|
size-limit report 📦
|
TL;DR
Removed the
advancedEnabled
property from the Account type and cleaned up a TODO comment.What changed?
advancedEnabled
boolean property from the Account type definition inuseApi.ts
newAccountStub
function instubs.ts
to remove theadvancedEnabled
property from the default account stubHow to test?
advancedEnabled
propertyadvancedEnabled
propertyWhy make this change?
The
advancedEnabled
property is no longer needed in the Account type, likely because this feature flag has been deprecated or the functionality has been restructured. Removing unused properties keeps the codebase clean and prevents confusion about which fields are actually used.Summary by CodeRabbit