Make labels on latency charts more clear #20
Conversation
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
Many people I showed the application to got confused by the Regional results. Most of them started to understand what's going on only after I explained that Regional is a case when the edge function always runs in Washington instead of the closest region to the client. It seems that the labels on the chart could be updated to remove this confusion and give more value to people that don't have time to dive deep into the logic of the app. Signed-off-by: Piotr Jastrzebski <[email protected]>
|
@haaawk is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
@leerob Would you be open to changing the names of the labels? I've shown this app to many people and most of them got really confused by the |
|
I wonder how we can make this more clear now with the addition of Node.js as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Many people I showed the application to got confused by the Regional results.
Most of them started to understand what's going on only after I explained that Regional is a case when the edge function always runs in Washington instead of the closest region to the client.
It seems that the labels on the chart could be updated to remove this confusion and give more value to people that don't have time to dive deep into the logic of the app.