Fix: Tag Interface Delete Button #104256
No reviewers
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#104256
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Evelinealy/flamenco:tag-interface"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Small update to PR #104244
I'm replacing the delete button next to the create tag button and putting it next to the name tags. I'm still working on removing the selecting because I don't want to remove any parts that may be important for the renaming.
I got it! Removed both the selection ability (safely) and the deletion now works where a user needs to only click the button once. Let me know if there's any bugs that you get. I tested it out and the CRUD operations work on my end.
@ -141,3 +135,3 @@
const tag_options = {
columns: [
{ title: "Name", field: "name", sorter: "string", editor: "input" },
{
Add this column to the end, so that it has the same layout as the job blocklist (there the ❌ is on the right as well).
@ -147,2 +164,4 @@
sorter: "string",
editor: "input",
vertAlign: "center",
width: 400,
Not sure if a fixed width is going to work well here, especially when the window gets resized.
@ -228,2 +247,2 @@
deleteTag() {
if (!this.selectedTag) {
deleteTag(tag) {
if (!tag) {
This shouldn't happen anyway, so you can just remove the entire conditional return here. Better to raise an error that you can see & debug (because of the
tag.id
access failing) than to silently ignore mistakes.@ -236,2 +254,3 @@
.deleteWorkerTag(tag.id)
.then(() => {
this.selectedTag = null;
this.tags = this.tags.filter((t) => t.id !== tag.id);
This can be removed. The SocketIO handling will already remove the tag, no matter who did the deletion.
I'm unsure if this is any better of a solution. I'm trying to work with the SocketIO, but removing some parts is tricky because it shows (obviously) in the backend that there is a removal of the tag, but it will not display on my table. With this solution, the user can see that a tag has been removed from both the frontend table and backend (like when trying to connect a tag to a worker).
That's for a different PR, then. This PR is for moving the 'delete' button, and because it removes the need for selection of tags, also remove that feature. If there is anything going wrong in the SocketIO signalling, or the handling of that, IMO that should be handled in a separate PR.
I've a made a few final changes, so that we can land this PR and include it in v3.3 :)