-
Notifications
You must be signed in to change notification settings - Fork 542
[TOOL-3691] Dashbaord: Keep project settings submit button always enabled #6467
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
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 #6467 +/- ##
=======================================
Coverage 54.80% 54.80%
=======================================
Files 875 875
Lines 54851 54851
Branches 3738 3738
=======================================
Hits 30062 30062
Misses 24695 24695
Partials 94 94
🚀 New features to boost your workflow:
|
apps/dashboard/src/app/team/[team_slug]/[project_slug]/settings/ProjectGeneralSettingsPage.tsx
Show resolved
Hide resolved
apps/dashboard/src/app/team/[team_slug]/[project_slug]/settings/ProjectGeneralSettingsPage.tsx
Show resolved
Hide resolved
size-limit report 📦
|
Merge activity
|
…bled (#6467) <!-- start pr-codex --> ## PR-Codex overview This PR focuses on simplifying the logic for determining if form fields are "dirty" before enabling the save button in the `ProjectGeneralSettingsPage`. It removes checks for dirty states, allowing the save button to be enabled regardless of whether the fields have been modified. ### Detailed summary - Removed `isNameDirty` check for the `name` field in `ProjectNameSetting`. - Removed `isDomainsDirty` check for the `domains` field in `AllowedDomainsSetting`. - Removed `isBundleIdsDirty` check for the `bundleIds` field in `AllowedBundleIDsSetting`. - Updated save button to always have `disabled: false` for all settings. - Kept `isPending` functionality unchanged based on `props.isUpdatingProject`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
51c487a
to
269fbe5
Compare
PR-Codex overview
This PR focuses on improving the handling of form state in the
ProjectGeneralSettingsPage.tsx
file by removing unnecessary checks for whether the form fields are dirty, simplifying the save button logic.Detailed summary
isDirty
checks forname
,domains
, andbundleIds
fields.disabled
property of save buttons tofalse
for all settings.isPending
property to only depend onprops.isUpdatingProject
.