refactor: ConfigProvider form dependency inversion for v4 #43207
+34
−13
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.
[中文版模板 / Chinese template]
🤔 This is a ...
🔗 Related issue link
same as #42604 #43023
close #42499
💡 Background and solution
📝 Changelog
☑️ Self-Check before Merge
🚀 Summary
🤖 Generated by Copilot at 479bd28
Refactored the form component and the config provider component to use a new
ValidateMessagesContext
to handle thevalidateMessages
prop. This improves the code quality and the consistency of the validation messages. Created a new filevalidateMessagesContext.tsx
to export the context.🔍 Walkthrough
🤖 Generated by Copilot at 479bd28
ValidateMessagesContext
instead of theRcFormProvider
to pass thevalidateMessages
prop from theConfigProvider
component (link, link, link, link, link, link)validateMessagesContext.tsx
file to export theValidateMessagesContext
as a React context (link)FormProvider
component to wrap theFormContext.Provider
component and pass thevalidateMessages
prop to the form components (link, link)arrow-parens
(link, link, link, link, link)