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

refactor: replace tailwindcss with unocss #86

Merged
merged 1 commit into from
Jul 22, 2024

Conversation

ruibaby
Copy link
Member

@ruibaby ruibaby commented Jul 22, 2024

使用 UnoCSS 代替 TailwindCSS,移除 class 的前缀并保证不会污染 Core 的样式。

/kind improvement

None

Signed-off-by: Ryan Wang <i@ryanc.cc>
@f2c-ci-robot f2c-ci-robot bot added kind/improvement Categorizes issue or PR as related to a improvement. release-note-none Denotes a PR that doesn't merit a release note. labels Jul 22, 2024
@f2c-ci-robot f2c-ci-robot bot requested review from guqing and JohnNiang July 22, 2024 06:28
Copy link
Collaborator

@JohnNiang JohnNiang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@f2c-ci-robot f2c-ci-robot bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2024
Copy link

f2c-ci-robot bot commented Jul 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JohnNiang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@f2c-ci-robot f2c-ci-robot bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2024
@f2c-ci-robot f2c-ci-robot bot merged commit e73ef06 into halo-sigs:main Jul 22, 2024
2 checks passed
@ruibaby ruibaby deleted the refactor/use-unocss branch July 22, 2024 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/improvement Categorizes issue or PR as related to a improvement. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants