-
Notifications
You must be signed in to change notification settings - Fork 37
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
Duplicated application groups #85
Comments
I saw this when the case was different in the annotation and the custom app, not sure if there are other cases where it happens as well. |
@ullbergm - that was my thought as I had problems with the case before. But I double-checked including seeing if there were any extra leading/trailing spaces and there are none I can see. Did the de-duplication work for you when the cases match between the ingress and custom app? |
It did. I think the problem is that when customApps are loaded from the config the group name is turned in to lower-case but that is not happening with ingressApps: @toboshii The current fix I put in is to normalize the group names when loaded from the config/kubernetes api. The drawback is that if the theme changes in the future then we may want to retain the case of the group names. Incidentally, there is also an issue if you have extra spaces like @angelnu said which is fixed with a strings.TrimSpace() when loading/comparing the objects. edit: changed my mind |
Thanks @ullbergm - I can confirm that after removing the capital case (Admin -> admin) then both groups are merged as expected. |
Describe the bug
Application groups injected via ingress annotations and customApps are not merged. This results in the group appearing twice:
I checked the that they written exactly the same:
Admin
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both apps showing in the same group
Screenshots
See above
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
NA
The text was updated successfully, but these errors were encountered: