refactor(TPopup): 用动画实现淡入淡出效果，并完成代码的重构和优化，提升性能

teacher-zhou commented 1 year ago

本次提交包含什么范围

[x] [fix]修复（对缺陷的修复）
[ ] [feat]功能（新功能、特性的开发）
[ ] [docs]文档（仅对当前版本的文档进行增加、完善和更新）
[x] [pref]性能（改进性能的代码更改）
[x] [refactor]重构（既不修复bug也不添加特性的代码更改）
[ ] [style]风格（不影响代码含义的更改(空白、格式化、缺少分号等)
[ ] [test]测试（添加缺失的测试或修改现有的测试）
[ ] [build]编译（影响构建系统或外部依赖的更改）
[ ] [ci]集成（对CI配置文件和脚本的更改）
[ ] [others]其他，请说明：

参考 https://www.conventionalcommits.org/zh-hans/v1.0.0/

关联的 ISSUE 编号（一行一个）

github-actions[bot] commented 1 year ago

Unit Test Results

:green_circle: Tests Passed | :stopwatch: 5s

:memo: Total	:heavy_check_mark: Passed	:x: Failed	:warning: Skipped
123	122	0	1

:pencil2: updated for commit 55b2ebf3

github-actions[bot] commented 1 year ago

查看测试结果 https://github.com/AchievedOwner/TDesignBlazor/runs/13677554787

pull-request-quantifier-deprecated[bot] commented 1 year ago

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

Quantification details

``` Label : Large Size : +149 -178 Percentile : 72.7% Total files changed: 11 Change summary by file extension: .xml : +10 -56 .razor : +6 -3 .cs : +41 -37 .csproj : +67 -56 .js : +25 -26 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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? :thumbsup: :ok_hand: :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

github-actions[bot] commented 1 year ago

查看测试结果 https://github.com/AchievedOwner/TDesignBlazor/runs/13677592301

tdesign-blazor / TDesignBlazor