Please check if your PR fulfills the following requirements:
[ ] Affected Tests have been added/altered (for bug fixes / features)
[ ] Docs have been reviewed and added/updated if needed (for bug fixes / features)
[X] Build was run locally and mvn install succeeds
Pull request type
Please check the type of change your PR introduces:
[X] Bugfix
[X] Feature
[ ] Code style update (formatting, renaming)
[X] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the current behavior?
Currently we run into a loop when fetching Connection Containers
We also do not fetch connectionContainers again if the initial Amount of possibilities has been reached -> no data reload even if more requestCredentials would be available
the label generation was using a lot of unnecessary state retrievals
atom in state loading did not always show the skeleton/loading card
What is the new behavior?
the fetch loop has been removed
connContainers are loaded again if new requestCredentials "arise"
label generation is simplified
atom loading ui is displayed appropriately for atom-cards
Pull request checklist
Please check if your PR fulfills the following requirements:
mvn installsucceedsPull request type
Please check the type of change your PR introduces:
What is the current behavior?
What is the new behavior?
Does this introduce a breaking change?