* fix: success feedback should display when pass hasFeedback prop and type valid value
* feat: optimize code
* feat: update test case
* feat: optimize code
* feat: optimize code
* feat: update demo
* feat: update test case
* feat: update demo
* feat: update test case
* feat: reset demo
* chore: init test
* test: rootClassName inject
* test: part of test
* chore: patch qrcode rootCls
* chore: part rootClassName
* chore: part rootClassName
* test: more test
* test: more test
* test: more test
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* test: more test
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: part rootClassName
* chore: fix lint
* chore: fix lint
* chore: ignore part of lint
* test: update snapshot
* test: fix test case
* chore: fix node test
* chore: adjust render logic
* fix: test
* test: update snapshot
* test: update
* refactor
* chore: fix require module logic
* Clarify error about children of Form.Item with `name`
This is a common error and the message as written was not very clear.
This should be more helpful pointing people in the right direction
* Update error message in test
* Clarify more error messages
Referring to "render props" is confusing because the docs don't explain what that is, and it's not really a prop.
* Update tests for new error messages
Also improve the test names for some
* Further test message updates
Missed a couple messages
* Add short URLs
* Update test error messages
* Apply suggestions from code review
* Apply suggestions from code review
Co-authored-by: Ell Bradshaw <joelbr@tailormed.co>
Co-authored-by: afc163 <afc163@gmail.com>