Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: support session audit log#16703

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
BrunoQuaresma merged 3 commits intomainfrombq/refactor-audit-log-row
Feb 26, 2025
Merged

Conversation

BrunoQuaresma
Copy link
Collaborator

Related to#15139

Demo:
Screenshot 2025-02-25 at 16 27 12

@BrunoQuaresma
Copy link
CollaboratorAuthor

@mafredri open questions:

  • We currently use the user field to fill the avatar. Since this is not related to a specific user, what kinda of avatar do you think we should use? 🤔
  • In the design that you shared in therelated issue, the tooltip had a "reason" section but I can't see a related field in the audit log response.

Copy link
Member

@mafredrimafredri left a comment

Choose a reason for hiding this comment

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

From a BE/implementation perspective, this LGTM!

return (
<Pill
css={styles.statusCodePill}
type={isHttp ? httpStatusColor(code) : code === 0 ? "success" : "error"}
Copy link
Member

Choose a reason for hiding this comment

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

Nice fix for this!

@@ -232,6 +227,19 @@ export const AuditLogRow: FC<AuditLogRowProps> = ({
);
};

function StatusPill({ code }: { code: number }) {
const isHttp = code >= 100;
Copy link
Member

Choose a reason for hiding this comment

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

Actually, a better measure of http status code may be whether or not this was a connect/disconnect action. Shell errors can be 0-255, but perhaps we should just mark them as 0/1 on the API side, wdyt?

Copy link
CollaboratorAuthor

Choose a reason for hiding this comment

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

Hm... I think it works 👍

BrunoQuaresmaand others added2 commitsFebruary 26, 2025 13:58
…LogDescription.tsxCo-authored-by: Mathias Fredriksson <mafredri@gmail.com>
@BrunoQuaresmaBrunoQuaresma merged commitf1b357d intomainFeb 26, 2025
30 checks passed
@BrunoQuaresmaBrunoQuaresma deleted the bq/refactor-audit-log-row branchFebruary 26, 2025 17:13
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsFeb 26, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@mafredrimafredrimafredri approved these changes

Assignees

@BrunoQuaresmaBrunoQuaresma

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@BrunoQuaresma@mafredri

[8]ページ先頭

©2009-2025 Movatter.jp