Skip to content
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(deps): update dependency antd to ^5.11.0 #458

Merged
merged 1 commit into from
Nov 3, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 3, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
antd (source) ^5.10.2 -> ^5.11.0 age adoption passing confidence

Release Notes

ant-design/ant-design (antd)

v5.11.0

Compare Source


  • Slider
    • 🆕 Slider 聚焦滑块时现在会显示 Tooltip。#​45653
    • 💄 优化 Slider 交互体验,点击轨道后可直接拖拽滑块。#​45651
  • InputNumber
    • 🆕 InputNumber 添加 changeOnBlur 属性以支持在失去焦点时不触发 onChange 事件。#​45395
    • 🐞 修复 InputNumber 组件在 Form 组件中使用并且启用 hasFeedback 时,反馈图标出现会使 InputNumber 失去焦点的问题。#​45632 @​MadCcc
    • 🐞 修复 InputNumber 动态改变 formatter 不生效的问题。#​45325
  • Table
    • 🆕 Table 组件 columnTitle 支持传入 render 方法。#​41937 @​Zhou-Bill
    • 🛠 重构 Table ref 支持 scrollTo 以滚动到目标 keyindextop#​45245
  • Tabs
    • 🆕 Tabs items 支持单个标签页设置 destroyInactiveTabPane#​45359
    • 🐞 修复 Tabs 的标签宽度存在小数时,滚动会出现抖动的问题。#​45370
  • ConfigProvider
  • 🆕 ColorPicker 组件 preset 新增 defaultOpen 属性,可控制预设颜色默认是否展开。#​45607 @​Wxh16144
  • 🆕 Select 组件支持 optionRender 方法。#​45529 @​RedJue
  • 🆕 Pagination 组件支持组合 simpleshowSizeChanger 使用。#​45538
  • 🆕 Spin 组件新增 fullscreen 属性,支持全屏展示。#​44986 @​Rafael-Martins #​45436 @​li-jia-nan
  • 🆕 Form validateFields 支持 dirty 参数以校验被修改过和校验过的字段。#​45389
  • 🆕 Watermark 支持 inherit 配置,关闭水印传导至弹出 Drawer 与 Modal。#​45319
  • 🆕 App 支持 component 以自定义渲染元素。#​45292
  • 🆕 Input 与 Input.TextArea 支持 count 自定义字符计数(例如固定 emoji 字符长度为 1);count.max 支持超出范围样式;将 emoji 计数还原为原生计数以解决 maxLengthvalue 不匹配的问题。#​45140
  • 🐞 修复 Dropdown 在点击菜单项关闭弹出框时不会触发 onOpenChange 的问题。#​45378
  • 💄 Modal 静态方法支持 styles 属性。#​45558 @​KotoriK
  • 💄 优化弹层组件的 z-index 逻辑,使其在默认情况下不会互相遮挡。#​45512 #​45490 @​kiner-tang

v5.10.3

Compare Source



Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Nov 3, 2023
@renovate renovate bot force-pushed the renovate/dependencies branch from 61c4db4 to 30ce853 Compare November 3, 2023 19:09

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@renovate renovate bot merged commit de4cbdc into main Nov 3, 2023
3 checks passed
@renovate renovate bot deleted the renovate/dependencies branch November 3, 2023 21:55
github-actions bot added a commit that referenced this pull request Nov 3, 2023
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> de4cbdc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants