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] History tab top margin / spacing (#9568) #9621

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

ValentinBouzinFiligran
Copy link
Member

Proposed changes

  • refacto jsx => tsx
  • margin fix on StixCoreObjectHistory

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

@ValentinBouzinFiligran ValentinBouzinFiligran added the filigran team use to identify PR from the Filigran team label Jan 16, 2025
Copy link

codecov bot commented Jan 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.26%. Comparing base (d61f670) to head (2519e6d).
Report is 13 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #9621   +/-   ##
=======================================
  Coverage   65.26%   65.26%           
=======================================
  Files         630      630           
  Lines       60244    60244           
  Branches     6760     6763    +3     
=======================================
  Hits        39319    39319           
  Misses      20925    20925           

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

@CelineSebe CelineSebe self-requested a review January 17, 2025 15:38
<div style={{ float: 'right' }}>
<SearchInput
variant="thin"
onSubmit={handleSearchEntity}
Copy link
Member

Choose a reason for hiding this comment

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

Is it possible to set directly "setEntitySearchTerm(value)" there?

Copy link
Member Author

Choose a reason for hiding this comment

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

I should write an anonymous function directly here and I don't find it great for readability

key={`latest_history_skel_${i}`}
dense
divider
button={false}
Copy link
Member

Choose a reason for hiding this comment

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

I think you can remove button={false}, it's deprecated

@CelineSebe
Copy link
Member

Tested ✅

@CelineSebe
Copy link
Member

I found a pre-existing bug. When I write in the left search bar, the same input appears in the search bar on the right:
image

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.

2 participants