fix: Proceed to next group in list if SubGroups is an empty slice #271
+15
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description
During the
getGroupByNamefunctiong.SubGroupscan not be nil and return an empty slice, which the recursivegetGroupByNamefunction call will return early instead of proceeding to the next group in the originalgroupslist. This occurs when there are two groups returned via theGetGroupsAPI call, and one of them has a child group and another one does not.Fixes #268
Type of change
How Has This Been Tested?
Create a parent group and a child group from the issue
Ensure there are no errors creating the CRs.
Checklist: