refactor: improve toBoxArray readability and type safety #4604
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.
🤔 这个分支是...
🔗 相关 issue 连接
💡 问题的背景&解决方案
背景:
原先
toBoxArray
函数在处理不同长度的数组输入时,逻辑分支较多且返回结构不统一。注释内标注的方向(top/right/bottom/left)存在重复与潜在歧义,且未对类型进行统一定义。解决方案:
BoxTuple<T>
类型,明确返回结构[top, right, bottom, left]
;📝 Changelog
toBoxArray
logic and introducedBoxTuple<T>
type for consistent tuple return. Simplified array handling and improved readability.toBoxArray
函数逻辑,引入BoxTuple<T>
类型以统一返回格式,简化分支逻辑并提升可读性。☑️ 自测
🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough