fix(TagInput): 修改 inputProps 中事件与 TagInput 事件冲突问题(#4802) #4935
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
#4802
💡 需求背景和解决方案
可能是 jsx 中会出现的问题
比如这个例子,使用解构赋值的方式向 MyComponent 传入了两个 onChange 事件,这时候 MyComponent 中接收到的 onChange 就是 [方法1, 方法2] 组成的数组,而并非期待的一个函数
解决方法:我创建了一个 inputPropsWithoutEvent 变量,这个变量会过滤 inputProps 中的事件,而事件则是放在组件调用的事件方法中去调用。我把 inputProps 中的方法放在第一执行顺位,以 onChange 事件为例,正常逻辑去想肯定是 input 先 change 再然后是 TagInput change。同样以上文的例子为例。
📝 更新日志
fix(TagInput): 修改 inputProps 中事件与 TagInput 事件冲突问题
本条 PR 不需要纳入 Changelog
☑️ 请求合并前的自查清单