-
Notifications
You must be signed in to change notification settings - Fork 331
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
fix(Form): fix nesting name underline error #3095
Merged
Merged
Conversation
This file contains 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
HaixingOoO
requested review from
honkinglin,
uyarn,
carolin913,
NWYLZW and
ZWkang
as code owners
September 12, 2024 05:36
/update-snapshot |
1 similar comment
/update-snapshot |
⏳ 正在运行快照更新。。。 CI: Open |
/update-snapshot |
⏳ 正在运行快照更新。。。 CI: Open |
uyarn
approved these changes
Sep 12, 2024
This was referenced Sep 12, 2024
Closed
Merged
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.
🤔 这个 PR 的性质是?
🔗 相关 Issue
💡 需求背景和解决方案
之前是使用
_
來拼接name,在一些name使用下划线时会导致有图上的bug,现在直接使用toString(例如:,
)来拼接📝 更新日志
fix(Form): 修复
name
使用下划线拼接的导致的bug本条 PR 不需要纳入 Changelog
☑️ 请求合并前的自查清单