-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: implement new table design #189
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
001139a
rename timestamp coloumn to time
kantord 4c2c604
make 'time' the first column
kantord 474f9a2
use relative date time format in alerts table
kantord e68e4c2
rename trigger type column to type
kantord 70ceabb
clamp trigger markdown to a single lineoverflowoverflow
kantord fa48c6e
remove code and file columns from alerts table
kantord a956b9e
rename trigger token column to event
kantord bc6542f
.
kantord 04860b3
implement event column content correctly
kantord 5e92cbe
implement type column values
kantord f7c9c73
add note about ongoing discussion on message type
kantord 3a778b2
fix mapping alerts type
kantord 2a742d8
Merge branch 'main' into alerts-table-refactor
kantord c07eeac
display detected problem properly
kantord 7d55f72
Merge branch 'main' into alerts-table-refactor
kantord b75fc79
configure alerts table width
kantord 60bda23
fix table column sizing using <ResizableTableContainer />
kantord ca3e01c
Merge branch 'main' into alerts-table-refactor
kantord e0fec1a
fix failing test
kantord 25369f8
make icon blue in alerts table
kantord File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for malicious package we can show the link to insights, it was already in place, I guess it could be very useful to show.
@jtenniswood maybe you didn't have an real example on that:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, if the entire table row is clickable, does it make sense to put another link to it?
I think that we should create an alert detail page 🤔 then we could put all these additional information there.
Actually I think that we can convert the current conversation page into an alert detail page? Basically keeping the current content but adding a header or sth similar where we can add details about the alert (I guess this could be hidden for conversations that don't have any alerts?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, but I also see the value to show the detail about a malicious package, maybe instead of a clickable row we could add a column e.g.
go to chat
I guess that James is not aware of this malicious package detail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I totally agree, I prefer that over a clickable row any day. It's much clearer user experience in my opinion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will mention this to James
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if that sub content should be on the sub page? I have also heard people wanting to be linked to the place where it happens in the conversation (also for secrets leaking).