fix(vue-component): [mind-map] border-radius & border #1510
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@GaoNeng-wWw is attempting to deploy a commit to the OpenTiny Team on Vercel. A member of the Team first needs to authorize it. |
|
[e2e-test-warn] 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 |
|
demo ^^^ |
zzcr
reviewed
Mar 26, 2024
GaoNeng-wWw
changed the title
AcWrong02
approved these changes
Mar 27, 2024
kagol
reviewed
Mar 28, 2024
zzcr
reviewed
Mar 30, 2024
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
zzcr
approved these changes
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: #1500
What is the new behavior?
Does this PR introduce a breaking change?
Other information