docs: RFC for SDK hooks approach for partner flexibility#1254
Merged
serikjensen merged 10 commits intomainfrom Apr 14, 2026
Merged
docs: RFC for SDK hooks approach for partner flexibility#1254serikjensen merged 10 commits intomainfrom
serikjensen merged 10 commits intomainfrom
Conversation
This was referenced Mar 18, 2026
9a0a1ea to
2f62ba7
Compare
2f62ba7 to
243cf59
Compare
krisxcrash
approved these changes
Mar 25, 2026
Contributor
|
@serikjensen does this still need to be merged? |
Follow-up to the UI flexibility exploration RFC with a concrete proposal based on working implementations from the SDK-470 branch. Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
c9d5572 to
9440f7b
Compare
Bring the RFC up to date with the actual UNSTABLE_Hooks codebase: - Update status from Draft to Implemented (UNSTABLE) - Add hook inventory table (7 hooks now shipping) - Replace generateSchema examples with buildFormSchema pattern - Document optionalFieldsToRequire partner API - Replace useEffect+reset with values+resetOptions pattern - Update return shape to actual nested structure - Replace per-hook FormProvider with SDKFormProvider - Add useDeriveFieldsMetadata, useSyncFieldErrors - Add prebuilt components section - Add optional entity ID / submit-time resolution pattern - Update error handling from aspirational to implemented - Update rollout and recommendations to reflect current state Made-with: Cursor
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
3 participants
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.
Summary
RFC proposing the hooks approach for partner UI flexibility, based on working implementations from PR #1239.
Covers fetch hooks, form hook anatomy, validation messages, form composition, conditional fields, and state taxes. Includes advantages, limitations, and recommendations.
Going to begin working towards implementation, but please review and provide any feedback!
Made with Cursor