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.

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

🐛 Handle case when application.archetypes is passed but null (#1707) #1710

Merged
merged 1 commit into from
Feb 28, 2024

Conversation

github-actions[bot]
Copy link

Resolves https://issues.redhat.com/browse/MTA-2320

  • Missed a case when calculating associated assessed archetypes to an
    application. If application is passed to the useFetchArchetypes query
    but application.archetypes is null, still returning all archetypes
    instead of an empty list.

Signed-off-by: Ian Bolton [email protected]
Signed-off-by: Cherry Picker [email protected]

Resolves https://issues.redhat.com/browse/MTA-2320

- Missed a case when calculating associated assessed archetypes to an
application. If application is passed to the useFetchArchetypes query
but application.archetypes is null, still returning all archetypes
instead of an empty list.

---------

Signed-off-by: Ian Bolton <[email protected]>
Signed-off-by: Cherry Picker <[email protected]>
@ibolton336 ibolton336 merged commit 3114082 into release-0.3 Feb 28, 2024
1 check passed
@ibolton336 ibolton336 deleted the cherry-pick-pr1707-release-0.3 branch February 28, 2024 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant