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] Bulk edition of status regression fix (#8393) #8400

Merged
merged 2 commits into from
Sep 20, 2024
Merged

Conversation

Archidoit
Copy link
Member

Proposed changes

Fix a regression: it was not possible anymore to bulk edit Status via the toolbar

Related issues

#8393

@Archidoit Archidoit added the filigran team use to identify PR from the Filigran team label Sep 18, 2024
@Archidoit Archidoit self-assigned this Sep 18, 2024
@Archidoit Archidoit linked an issue Sep 18, 2024 that may be closed by this pull request
@Archidoit Archidoit marked this pull request as draft September 18, 2024 15:23
@Archidoit Archidoit marked this pull request as ready for review September 19, 2024 08:14
Copy link

codecov bot commented Sep 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.14%. Comparing base (d6c9835) to head (c0cddce).
Report is 11 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #8400   +/-   ##
=======================================
  Coverage   66.13%   66.14%           
=======================================
  Files         597      597           
  Lines       60374    60374           
  Branches     6191     6192    +1     
=======================================
+ Hits        39931    39936    +5     
+ Misses      20443    20438    -5     

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

@SouadHadjiat
Copy link
Member

is it possible to add a non regression test for this usecase ?

labo-flg
labo-flg previously approved these changes Sep 20, 2024
if (selectedTypes.length === 1) {
[selectedType] = selectedTypes;
} else {
throw Error('It is not possible to bulk edit statuses if more than one entity type is selected.');
Copy link
Member

Choose a reason for hiding this comment

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

that would show as an error in the UI ?

Copy link
Member Author

Choose a reason for hiding this comment

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

theoretically, it's not possible to have this error since we check in the code that only one entity type is selected. It's to prevent bad changing of code in the future if someone don't exactly know what he is doing ;)

@labo-flg
Copy link
Member

I can now update vulnerabilities status in mass ops from Vuln list, but not from Entities view. Is it expected ?

@labo-flg
Copy link
Member

I can now update vulnerabilities status in mass ops from Vuln list, but not from Entities view. Is it expected ?

status is open vocab, might be different from entities to entities, so definitely not an issue.

@Archidoit
Copy link
Member Author

@labo-flg Yes it's expected because entities of different type have different possible values for 'status'

@Archidoit Archidoit merged commit 1f099b8 into master Sep 20, 2024
6 checks passed
@Archidoit Archidoit deleted the issue/8393 branch September 20, 2024 08:02
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.

Bug/Regression - Bulk edition of status not possible
3 participants