fix(pager): [pager] fix pager css vars default value error

[gimmyhehe]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Updated the version of the @opentiny/vue-theme package to 3.18.3.

• Bug Fixes

  • Corrected the CSS variable for pager text padding to ensure proper calculation, enhancing layout consistency.

[coderabbitai]

Walkthrough

The pull request includes two main updates: the version number of the @opentiny/vue-theme package has been incremented from 3.18.2 to 3.18.3 in the package.json file. Additionally, modifications have been made to the CSS variable --ti-pager-normal-text-padding-left in the vars.less file, correcting its definition to ensure accurate padding calculations based on the --ti-common-space-base variable.

Changes

File	Change Summary
packages/theme/package.json	Updated version from 3.18.2 to 3.18.3.
packages/theme/src/pager/vars.less	Corrected definition of --ti-pager-normal-text-padding-left for accurate padding calculation.

Possibly related PRs

• fix(pager): [pager] fix pager hover style #2111: Changes to the pager component's CSS variables, related to updates in the vars.less file.
• refactor(pager): [pager] refactor pager style #2162: Modifications in the vars.less file for the pager component, aligning with the main PR's changes.
• refactor(pager): [pager] delete useless code #2198: Deletions and modifications in the index.less and vars.less files for the pager component, relevant to the main PR.
• refactor(theme): [input] refactor textarea theme vars #2281: Updates to the textarea component's theme variables, following a similar pattern to the main PR.
• refactor(popconfirm): [popconfirm] refactor theme vars #2282: Refactor of the Popconfirm component's theme variables, indicating a broader effort in CSS variable standardization.

Suggested reviewers

• zzcr

🐰 In the meadow, changes bloom,
A version update clears the gloom.
CSS variables dance and play,
Padding fixed, hip-hip-hooray!
With every tweak, our theme's a delight,
Hopping forward, everything feels right! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between cf5f8ea and 66074a1.

📒 Files selected for processing (2)

• packages/theme/package.json (1 hunks)
• packages/theme/src/pager/vars.less (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• packages/theme/package.json

🧰 Additional context used

🔇 Additional comments (1)

packages/theme/src/pager/vars.less (1)

52-52: Correct CSS variable calculation syntax

This change fixes the syntax error in the calc() function and properly sets the fallback value for --ti-common-space-base. The modification ensures that if --ti-common-space-base is not defined, it will use 14px as the base value for the calculation.

This correction resolves the issue mentioned in the PR objectives regarding the pager CSS vars default value error.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[chenxi-20]

默认值应该是个4px才对呀