Love your diff component! Small issue though, the line numbers aren't aligned - I guess it has to do with the text wrapping?

Love your diff component! Small issue though, the line numbers aren't aligned - I guess it has to do with the text wrapping?

Good catch! I will play around with smaller viewports and see what other bugs I can fix. Thanks.

I like the color-coded pills for status codes, but wonder if it will be unclear to some users what they represent. Maybe they could say Status 200 or Status: 200 instead of just 200.

I denied some of the Chromatic changes - it's all to do with indentations making values not line up with their headers. Not sure what caused it.

Does this handle pagination?

Does this handle pagination?

Nops, but I can do it tomorrow - it would be a diff PR tho. What do you think? Or the port thing should be a priority?

I like the color-coded pills for status codes, but wonder if it will be unclear to some users what they represent. Maybe they could say Status 200 or Status: 200 instead of just 200.

I think HTTP status is very well known 🤔 . For this layout specifically, adding the Status on every row can be too much visually because it increases the "accent color" area. I would wait for users to complain about that. But, if you think we should, I would be happy to add. Here is a comparison:

Sure, let's leave the status code as just the number and see if people ask about it.

I denied a few more Chromatic changes, this time it's just that a color change you made affected the Schedule switch, I don't think it looks "on" enough in the dark blue-grey color.

I made some minor updates:

• on auditXService I updated the invoke to use only one function that loads the count and the results. Having multiple invokes doesn't guarantee both services are completed at the end so we would have to use parallel states making it more complex than necessary only to load the count.
• The URL also changes on pagination so it can be a shareable URL