-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
feat: support changing attachment display name #6504
feat: support changing attachment display name #6504
Conversation
Signed-off-by: Ryan Wang <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6504 +/- ##
============================================
+ Coverage 58.18% 58.24% +0.06%
- Complexity 3774 3777 +3
============================================
Files 651 651
Lines 22125 22128 +3
Branches 1538 1538
============================================
+ Hits 12873 12889 +16
+ Misses 8641 8630 -11
+ Partials 611 609 -2 ☔ View full report in Codecov by Sentry. |
ui/console-src/modules/contents/attachments/components/DisplayNameEditForm.vue
Outdated
Show resolved
Hide resolved
Signed-off-by: Ryan Wang <[email protected]>
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[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 |
What type of PR is this?
/area ui
/kind feature
/milestone 2.19.x
What this PR does / why we need it:
支持修改附件的显示名称。
Fixes #4294
Does this PR introduce a user-facing change?