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

[frontend] Fix correlated cases is not working #4818

Merged
merged 6 commits into from
Nov 5, 2023

Conversation

Megafredo
Copy link
Member

Proposed changes

  • Updating the ternary operator in the "CaseIncidentDetail" file
  • Adding the ternary operator in the "ReportDetail" file to replace empty space with '-'

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@Megafredo Megafredo added the filigran team use to identify PR from the Filigran team label Oct 31, 2023
@Megafredo Megafredo added this to the Release 5.11.13 milestone Oct 31, 2023
@Megafredo Megafredo self-assigned this Oct 31, 2023
@Megafredo Megafredo linked an issue Oct 31, 2023 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Oct 31, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f091a20) 0.00% compared to head (b0daf11) 0.00%.
Report is 9 commits behind head on master.

❗ Current head b0daf11 differs from pull request most recent head 78ef9fd. Consider uploading reports for the commit 78ef9fd to get more accurate results

Additional details and impacted files
@@      Coverage Diff       @@
##   master   #4818   +/-   ##
==============================
==============================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jpkha jpkha self-requested a review November 2, 2023 06:41
@@ -233,7 +233,7 @@ const CaseIncidentDetails: FunctionComponent<CaseIncidentDetailsProps> = ({
{t('Correlated cases')}
</Typography>
<List classes={{ root: classes.relatedContainers }}>
{expandable
{(data.relatedContainers?.edges && data.relatedContainers.edges.length >= 2)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure, let's talk about that

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to extract the filtering of the list before the return and check that this computed list as at least one element

@SamuelHassine SamuelHassine removed this from the Release 5.11.13 milestone Nov 4, 2023
@SamuelHassine SamuelHassine merged commit 87d4c38 into master Nov 5, 2023
3 checks passed
@SamuelHassine SamuelHassine deleted the bug/4803-correlated-cases-is-not-working branch November 5, 2023 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran team use to identify PR from the Filigran team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Correlated cases is not working
4 participants