docs(FR-2897): clarify modal footer prop-first guidance in react-modal-drawer skill#7420
Merged
Merged
Conversation
Member
Author
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 required 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. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the react-modal-drawer skill documentation to steer implementers toward using BAIModal/antd’s built-in footer props (onOk, onCancel, okText, cancelText, okButtonProps, confirmLoading) as the default, and frames custom footer overrides as a last resort.
Changes:
- Rewrites Section 6 to be prop-first for standard OK/Cancel behavior, including guidance to bind mutation pending state via
confirmLoading. - Adds explicit “custom
footeronly when necessary” criteria and keeps the BAIFlex +BAIButton.actionexample under that bucket. - Introduces an anti-pattern example and updates the verification checklist to reflect the new guidance.
1be5602 to
961abf6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Resolves #7419 (FR-2897)
Summary
react-modal-drawerskill so the default guidance is to use the modal's built-in props (onOk,onCancel,okText,cancelText,okButtonProps,confirmLoading) — withconfirmLoadingexplicitly bound to the mutation'sisInFlight/isPending.footerto a last resort with three concrete justifications (third button, non-standard layout, non-button content), and kept the BAIFlex/Reset example under that bucket.confirmLoadingwas missed.confirmLoading, (c) BAIFlex +BAIButton.actiononly when a custom footer is justified.Context
PR-review thread on FR-2862 / VFolderDeployModal surfaced that the skill's prior wording (custom-footer example as the leading pattern) was nudging implementers toward reimplementing the standard footer. The Teams discussion is linked on the Jira issue.
Test plan
react-modal-drawer/SKILL.mdend-to-end — section 6 leads with props, custom footer is clearly framed as a last resort.