-
Notifications
You must be signed in to change notification settings - Fork 447
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
Fixes duplicate tree view add button for closed Controlled Vocabularies #3350
Conversation
@tdonohue I can port this change if it gets approved, unless I need to port it first, in which case, I will do that. |
@aseyedia : You do not need to port this PR prior to review. In fact, we have an automated porting process which is triggered if we merge a PR with a |
Hi @aseyedia, |
Finally got around to resolving the commit. Let me know if there are any issues. |
@aseyedia : This PR now has lint errors:
You need to use the (newly added) |
I feel like someone already fixed this issue: dspace-angular/src/app/shared/form/vocabulary-treeview/vocabulary-treeview.component.html Lines 21 to 24 in bf20787
I'm going to close this PR. |
References
Fixes #3325
Description
The Controlled Vocabulary tree view was displaying two "Add" buttons, one enabled and one disabled, for closed Controlled Vocabularies.
You can read more here.
Instructions for Reviewers
Minor change. I just removed one of the excess buttons and moved the conditional logic to the
[disabled]
parameter in the button class.To test it, try opening up a closed Controlled Vocabulary tree view and observing the "Add" button to make sure it's disabled and that there's only one of them.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!
main
branch of code (unless it is a backport or is fixing an issue specific to an older branch).npm run lint
npm run check-circ-deps
)package.json
), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.