-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Issue 1706 tag rename - finishing #2989 #3469
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
Conversation
• repurpose RenameFolderModal.styl to RenameModal so it is more generic
…er via the TagSelect component
|
@AWolf81 Could you investigate the failing check of the CI? |
|
@Flexo013 sure, I've checked it and fixed the build. Update |
|
@AWolf81 can you change the style to of the way we currently styling right now? Also the rename modal background doesn't match with some of the theme |
|
@ZeroX-DG Theme should be OK now. Please have a look. I've noticed one point that could be improved. If you clicked on a tag to rename and click Update 02.04.2020 |
ZeroX-DG
left a comment
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.
Sorry for the wait @AWolf81 LGTM 🎉 I think Travis got some error with it, not just you, Travis not running on many PR. I think we can try switching to something like Github Action 😄
|
Totally missed the pings, thanks for wrapping this up @AWolf81! |
Description
@khaliqgant I hope it's OK that I'm adding the requested changes from your PR #2989.
My PR adds a dialog if the new tag is matching an existing tag and shows a warning dialog.
@ZeroX-DG can you please check if the feature is now like you expect it? Please also check if the copy of the dialog is OK.
Linting issue is present here too. I've commited with
--no-verifyoption. Linting will be fixed in my other open PR.Issue fixed
#1706
Type of changes
Checklist:
Example merge warning (tag was 2nd and renamed to react - react tag already exists)
