Debugger 2.0 (Dec 3rd) #987
-
|
Background: we want customers to easily locate new errors and access the information they need I'd like to get feedback on overall components usage and overall interaction |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
Hi @sang-yeo This is a pretty big flow of many screens. I don't think a 20 minute slot is an appropriate amount of time to review an entire feature in. So to help us out, do you have specific questions regarding component usage you'd like to cover? Any that caused concerns in testing? Any that cause concern with the dev team? Any specific areas that you are unsure if you have used the right component for the right interaction? Anything that didn't have enough documentation on? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I agree this is a big flow of many screen. Lets me list it out.
|
Beta Was this translation helpful? Give feedback.
-
|
So much better! Thank you! 🙏 |
Beta Was this translation helpful? Give feedback.
-
It's still in development, but it will likely look pretty close to this (for table pages that have different URLs):
Here's the in-progress design and spec if you want to see how it's shaping up.
This may have to be a link instead of a button (see Discussion #848), so I'd recommend reaching out to your engineers. For the icon: If you find through user testing that it helps add clarity, add the icon! If there's no meaningful difference, you don't need it. See the last paragraph in our "Composing a Button" guidelines (it applies to anchors too): "Pair text with an icon only if the icon clarifies the meaning of the button."
I assume it's pretty easy for a customer to redo the filters if they accidentally clear them? And it has no effect on anything outside of filtering the table on the page? Destructive buttons should only be used when the action "could be difficult to reverse"
imo the up and down arrows could almost seem like you're expanding or shrinking the modal (but that could just be me). You could use the Pagination component here (even with the left/right arrows) in a Modal Footer. We've never seen this kind of Modal interaction/layout before, so using Pagination here would also be worth testing. If any customer issues show up because of the component, we'd love to know, too! |
Beta Was this translation helpful? Give feedback.
-
|
@serifluous Thanks for answering all my questions. In this case, a user only has one event, seems like showing the total number of the event under the table is visually off. What do you suggest? |
Beta Was this translation helpful? Give feedback.
-
|
You could probably remove/hide the pagination component entirely in a case like this since you have the "Showing 1 of 1" text at the top of the table. But I'll take this case into consideration as we continue work on Pagination design. I have a hunch we'll have the component just push that "1 of 1" text all the way to the right edge of the table—not completely sure yet though. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @sang-yeo Other than @serifluous's comments, the only other thing I'd add pertains to:
I think the word Export makes the most sense here since the user would be getting the logs in a different format. It looks like @ctecks gives similar feedback here: #990 (comment), which you may have already heard about. |
Beta Was this translation helpful? Give feedback.
It's still in development, but it will likely look pretty close to this (for table pages that have different URLs):
Here's the in-progress design and spec if you want to see how it's shaping up.
This may have to be a link instead of a button (see Discussion #848), so I'd recommend reaching out to your engineers. For the icon: If you find through user testing that it helps add clarity, add the icon! If there's no meaningful difference, you don't need it.
See the last paragraph in our "…