Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Renaming bouquet bug #33

Closed
vpont opened this issue Sep 8, 2020 · 2 comments
Closed

Renaming bouquet bug #33

vpont opened this issue Sep 8, 2020 · 2 comments
Assignees
@DYefremov
Labels
bug

Comments

@vpont
Copy link
Contributor

vpont commented Sep 8, 2020

I've found out that renaming a bouquet results in losing all the custom renames of the services in that bouquet.
Way to reproduce:

  1. Rename a few services in a bouquet with "Rename for this bouquet"
  2. Rename the bouquet (Ctrl-E)
  3. Change the active bouquet
  4. Go back to the renamed bouquet

Now all renamed services will have the default names.
@DYefremov DYefremov added the bug label Sep 8, 2020
@DYefremov DYefremov self-assigned this Sep 8, 2020
DYefremov added a commit that referenced this issue Sep 8, 2020
@DYefremov
renaming bouquet fix [losing custom names](#33)
ee462b2
@DYefremov
Copy link
Owner

Hi. Please test it.

@vpont
Copy link
Contributor Author

vpont commented Sep 8, 2020

I can confirm it's working as expected now 👍

DYefremov added a commit that referenced this issue Sep 8, 2020
@DYefremov
renaming bouquet fix [losing custom names](#33)
555699c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DYefremov DYefremov

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vpont @DYefremov