Closed zzcr closed 1 month ago
The pull request involves a systematic renaming of CSS custom properties across various LESS files to enhance naming consistency and clarity. The prefixes for color and input-related variables have been standardized from --tv-common-
and --ti-
to --tv-
. This change affects multiple variables related to colors, fonts, borders, and sizes, while maintaining the original functionality and structure of the styles. The modifications focus on improving code maintainability and readability without altering the visual representation of components.
File Path | Change Summary |
---|---|
packages/theme/src/base/vars.less |
Renamed CSS custom properties to standardize naming conventions, changing prefixes from --tv-common- to --tv- . |
packages/theme/src/input/index.less |
Updated CSS variables from --ti- to --tv- , ensuring consistency in input component styling. |
packages/theme/src/input/vars.less |
Renamed input-related CSS custom properties from --ti- to --tv- , enhancing naming consistency. |
enhancement
🐇 In the garden of code, we hop and play,
With colors and styles, we brighten the day.
Renaming our variables, a tidy delight,
Consistency blooms, making everything right.
So here's to our changes, both clever and bright,
A theme that unites, in the soft morning light! 🌼
packages/theme/src/input/index.less (13)
`26-26`: **LGTM!** The change is consistent with the overall theme variable renaming and the usage is correct. --- `31-31`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. Also applies to: 34-34 --- `40-43`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. --- `57-57`: **LGTM!** The change is consistent with the overall theme variable renaming and the usage is correct. --- `67-67`: **LGTM!** The change is consistent with the overall theme variable renaming and the usage is correct. --- `73-73`: **LGTM!** The change is consistent with the overall theme variable renaming and the usage is correct. --- `78-78`: **LGTM!** The change is consistent with the overall theme variable renaming and the usage is correct. --- `83-83`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. Also applies to: 86-86, 89-89 --- `99-100`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. Also applies to: 104-104 --- `110-110`: **LGTM!** The change is consistent with the overall theme variable renaming and the usage is correct. --- `116-123`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. Also applies to: 129-129 --- `135-135`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. Also applies to: 139-139, 152-152, 156-156, 161-161, 167-167, 172-172, 183-183, 189-189, 196-196, 204-204, 207-210, 213-213 --- `230-231`: **LGTM!** The changes are consistent with the overall theme variable renaming and the usage is correct. Also applies to: 235-236, 250-250, 252-252, 257-257, 259-259, 264-264, 266-266, 290-290, 345-348
[e2e-test-warn] The component to be tested is missing.
The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".
Please make sure you've read our contributing guide
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
New Features
Bug Fixes
Chores