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

add license banner for ui packages #184

Merged
merged 3 commits into from
Feb 5, 2025

Conversation

warjiang
Copy link
Contributor

What type of PR is this?
/kind feature

What this PR does / why we need it:
PR #176 has already add license check for code across the project, there is need to add license for bundle ouput of ui packages.

before:
image

after:
image

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

@karmada-bot karmada-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 27, 2025
@karmada-bot karmada-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 27, 2025
@warjiang
Copy link
Contributor Author

/assign @RainbowMango @samzong

@RainbowMango RainbowMango added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jan 27, 2025
Copy link
Member

@samzong samzong left a comment

Choose a reason for hiding this comment

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

From the perspective of code reuse and maintainability, should the LicenseBanner be abstracted into a public function? It seems that there is a high degree of code overlap

@warjiang warjiang force-pushed the feat/add-license-build branch 2 times, most recently from 893d07a to e4881d8 Compare February 5, 2025 07:36
@warjiang
Copy link
Contributor Author

warjiang commented Feb 5, 2025

From the perspective of code reuse and maintainability, should the LicenseBanner be abstracted into a public function? It seems that there is a high degree of code overlap

Yes, and thanks for your suggesion, I add @karmada/utils package which located in packages/utils, and repo under the ui folder can share getLicense functions.

…on-overlay/xterm-addon-zmodem

Signed-off-by: warjiang <1096409085@qq.com>
Signed-off-by: warjiang <1096409085@qq.com>
Signed-off-by: warjiang <1096409085@qq.com>
@warjiang warjiang force-pushed the feat/add-license-build branch from e4881d8 to 8227f72 Compare February 5, 2025 07:48
Copy link
Member

@samzong samzong left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

nice job.

@karmada-bot karmada-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2025
@karmada-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: samzong

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

@karmada-bot karmada-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 5, 2025
@karmada-bot karmada-bot merged commit be1beb1 into karmada-io:main Feb 5, 2025
7 checks passed
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/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants