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

front: fix stdcm conflicts not being properly displayed #9631

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

SharglutDev
Copy link
Contributor

@SharglutDev SharglutDev commented Nov 7, 2024

The display of stdcm results is depending on the presence of path propertie coming from the stdcm response path. PathProperties was saved only if the stdcm response was success, not with conflicts status.

fix #9628

@SharglutDev SharglutDev requested a review from a team as a code owner November 7, 2024 12:07
@codecov-commenter
Copy link

codecov-commenter commented Nov 7, 2024

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 42.50%. Comparing base (0e1ea9b) to head (f49fdcf).
Report is 6 commits behind head on dev.

Files with missing lines Patch % Lines
...nt/src/applications/stdcm/hooks/useStdcmResults.ts 0.00% 7 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@             Coverage Diff              @@
##                dev    #9631      +/-   ##
============================================
- Coverage     42.51%   42.50%   -0.02%     
  Complexity     2271     2271              
============================================
  Files          1311     1311              
  Lines        105413   105410       -3     
  Branches       3297     3297              
============================================
- Hits          44812    44800      -12     
- Misses        58655    58664       +9     
  Partials       1946     1946              
Flag Coverage Δ
core 75.05% <ø> (ø)
editoast 73.66% <ø> (-0.05%) ⬇️
front 18.79% <0.00%> (+<0.01%) ⬆️
gateway 2.19% <ø> (ø)
osrdyne 3.28% <ø> (ø)
railjson_generator 87.49% <ø> (ø)
tests 86.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Copy link
Contributor

@achrafmohye achrafmohye left a comment

Choose a reason for hiding this comment

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

LGTM and tested 👍

The display of stdcm results is depending on the presence of path propertie coming from the stdcm response path.
PathProperties was saved only if the stdcm response was success, not with conflicts status.

Signed-off-by: SharglutDev <[email protected]>
@SharglutDev SharglutDev force-pushed the pfn/front/fix-stdcm-conflicts branch from 6fe9dc4 to f49fdcf Compare November 7, 2024 12:26
Copy link
Contributor

@clarani clarani left a comment

Choose a reason for hiding this comment

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

LGTM ✅

@SharglutDev SharglutDev added this pull request to the merge queue Nov 7, 2024
Merged via the queue into dev with commit 7fcc66c Nov 7, 2024
24 checks passed
@SharglutDev SharglutDev deleted the pfn/front/fix-stdcm-conflicts branch November 7, 2024 13:19
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.

lmr: conflicts aren't displayed in front end, though the response has some
4 participants