-
Notifications
You must be signed in to change notification settings - Fork 544
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
Implement tag renaming #1165
base: master
Are you sure you want to change the base?
Implement tag renaming #1165
Conversation
Isn't it better to just actually rename the tag (update |
I've fixed the CI https://github.com/vladisslav2011/gqrx/tree/pi-rename-tag, but it does not work as expected. It tries to create a new tag instead of renaming and does wrong things when a tag is renamed to an existing name. I think, renaming should fail if the name, we are trying to rename to, already exists... |
I've added another commit to https://github.com/vladisslav2011/gqrx/tree/pi-rename-tag |
If there is an option to delete tag as user I would expect it will be also possible to create a tag. Yes, it is not working right now, but that can be fixed. |
Adding a tag and not assigning it to a bookmark looks pointless to me. It is still possible to create a 'floating' tag, that is not assigned to a bookmark (add a tag to a single bookmark, then remove it from the bookmark), but this tag will always get filtered out in |
7bbbdeb
to
3244ae3
Compare
Lets keep the focus on the subject of renaming. Thx @vladisslav2011 for the suggestions, I have kind of backported them to the code and tested and they work like a charm. |
Btw I'm getting |
I have no idea why this warning is emitted... |
3244ae3
to
20dc817
Compare
return false; | ||
|
||
if (oldName == newName) | ||
return false; |
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.
Lines 300..310 can be removed. I missed the same check at the line 254.
Or it may be better to remove check on line 254 as it looks better to compare trimmed strings.
The It is more convenient for me to point at code rather than on the person, it usually creates less friction :) |
Sorry :-) |
No description provided.