[frontend] fix call to stixCoreRelationshipsDistribution #6580
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.
If a country has a marking unavailable for a user, the dashboard query
stixCoreRelationshipsDistribution
crashes because said country is Restricted.This is due to PR #6323.
Now the
relationshipDistributions
data are checked and returned with "Restricted" representative if the user cannot access one this side of the relationship. Before they were filtered out, leading to inconsistencies (see #6319).The bug happens because we do a
...on Country { name }
and name is non-nullable, but will be null because it's restricted.