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

[backend/frontend] Danger zone: Remove FF (#8284) #8905

Merged
merged 4 commits into from
Nov 7, 2024

Conversation

marieflorescontact
Copy link
Member

@marieflorescontact marieflorescontact commented Nov 5, 2024

Proposed changes

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 (coverage and e2e)
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality

Further comments

@marieflorescontact marieflorescontact self-assigned this Nov 5, 2024
Copy link

codecov bot commented Nov 5, 2024

Codecov Report

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

Project coverage is 65.47%. Comparing base (99deaea) to head (ac16009).
Report is 4 commits behind head on release/6.4.0.

Files with missing lines Patch % Lines
...pencti-graphql/src/database/data-initialization.js 0.00% 7 Missing ⚠️
Additional details and impacted files
@@                Coverage Diff                @@
##           release/6.4.0    #8905      +/-   ##
=================================================
+ Coverage          64.33%   65.47%   +1.14%     
=================================================
  Files                608      609       +1     
  Lines              58054    58563     +509     
  Branches            6409     7528    +1119     
=================================================
+ Hits               37348    38346     +998     
+ Misses             20706    20217     -489     

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

@marieflorescontact marieflorescontact marked this pull request as ready for review November 5, 2024 10:57
@marieflorescontact marieflorescontact added the filigran team use to identify PR from the Filigran team label Nov 5, 2024
@@ -467,7 +467,7 @@ const Group = ({ groupData }: { groupData: Group_group$key }) => {
</Grid>
<GroupEdition
groupId={group.id}
disabled={!isAllowed}
disabled={!isAllowed && isSensitive}
Copy link
Member

Choose a reason for hiding this comment

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

why this change ?
I would naively think that isAllowed is always true if isSensitive is false (a non-sensitive zone is always granted).

Copy link
Member Author

Choose a reason for hiding this comment

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

because the edit button was disabled for non sensitive Group/Role if user was not allowed (not allowed to modified sensitive Group/Role )

Archidoit
Archidoit previously approved these changes Nov 7, 2024
@Archidoit
Copy link
Member

Archidoit commented Nov 7, 2024

The Danger Zone button doesn't seem well aligned with the text (it is a bit lower)

image

@Archidoit Archidoit dismissed their stale review November 7, 2024 09:08

button design

@marieflorescontact
Copy link
Member Author

The Danger Zone button doesn't seem well aligned with the text (it is a bit lower)

image

well in fact this is an illusion:
Capture d'écran 2024-11-07 101153

@Archidoit
Copy link
Member

The Danger Zone button doesn't seem well aligned with the text (it is a bit lower)
image

well in fact this is an illusion: Capture d'écran 2024-11-07 101153

yes the text in the button is aligned with the text, but the button itself is not aligned... Only design question I don't know if we let that :)

@marieflorescontact
Copy link
Member Author

marieflorescontact commented Nov 7, 2024

yes the text in the button is aligned with the text, but the button itself is not aligned... Only design question I don't know if we let that :)

I don't see what is not aligned, could you explain? 💐

@marieflorescontact marieflorescontact merged commit 4c3db1a into release/6.4.0 Nov 7, 2024
5 checks passed
@marieflorescontact marieflorescontact deleted the issue/8284_chunk5 branch November 7, 2024 14:49
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.

4 participants