-
Notifications
You must be signed in to change notification settings - Fork 16
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
Enable deletion of resolved reference tags #741
Enable deletion of resolved reference tags #741
Conversation
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.
A few code changes to simplify the JSX logic
frontend/lit/TagReferences/Main.js
Outdated
}> | ||
{this.state.showFullTag | ||
? tag.get_full_name() | ||
: tag.data.name} | ||
</span> | ||
))} | ||
{selectedReferenceUserTags |
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.
this is also too complicated; can we generate the list of items as just JS code as a variable above in the render method, not within the JSX component
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.
This has been simplified after other refactors; since its just a single line filter now I don't think it would make much sense to define it in the render method
hawc/static/css/hawc.css
Outdated
border: 0.15rem dotted #ffffff; | ||
color: maroon; | ||
background-color: #ffffff; | ||
border: 0.15rem dotted maroon; |
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.
add some transparency too?
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.
@shapiromatron I did some refactoring outside of your recommendations, which outdates one of your comments; let me know if you like these refactors as a whole and if you're fine with the compromise on your one comment. |
Changes look good! |
This is an example of how we can handle deleting resolved tags when conflict resolution is enabled.
When user tags don't exist for a reference, the resolved tags are added by default:
From here, a user can add additional tags and also remove resolved tags:
If a resolved tag is removed, it is still displayed with a strikethrough. Clicking on it again will reapply it.