You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement - what kind of business use case are you trying to solve?
This is a user experience-related issue.
Problem - what in Jaeger blocks you from solving the requirement?
Going through the getting started page, the user may simply want to directly copy and paste the written code using the copy button.
This is not possible because the command prompt symbol is also copied with the code, requiring the user to manually edit the copied text to prevent errors if directly pasted.
This defeats the purpose of the copy functionality.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Separate the prompt symbol display from the actual command, so the copy works as normal.
The text was updated successfully, but these errors were encountered:
I agree, I also found it annoying. I don't know how easy it is to display the prompt symbol via css, the simple alternative is to just remove it from the command.
I think the prompt symbol is useful to differentiate the command from the stdout, but in the case of the getting started page, these are only commands.
Requirement - what kind of business use case are you trying to solve?
This is a user experience-related issue.
Problem - what in Jaeger blocks you from solving the requirement?
Going through the getting started page, the user may simply want to directly copy and paste the written code using the copy button.
This is not possible because the command prompt symbol is also copied with the code, requiring the user to manually edit the copied text to prevent errors if directly pasted.
This defeats the purpose of the copy functionality.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Separate the prompt symbol display from the actual command, so the copy works as normal.
The text was updated successfully, but these errors were encountered: