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
Is your feature request related to a problem? Please describe.
Several tickets exist that query how to display lengthy strings inside the debugger frame.
These tickets are all locked, more recently with a comment similar to "dlv-dap doesn't support this yet".
Describe the solution you'd like
Document the approach a user is supposed to take to view truncated long strings.
Describe alternatives you've considered
Add this feature to dlv-dap. This seems like a lot of work for something that can be covered in the short term with documentation.
Additional context
Yes, there is probably an article or note somewhere that explains this, but if it doesn't appear in the top ten when searching Google it essentially does not exist to the average programmer.
The text was updated successfully, but these errors were encountered:
Agreed - you might want to go back into one of the old issues and flag that there's documentation to cover this circumstance atm. E.g. the following is the top Google response to "vscode go delve trimmed string": #645
Is your feature request related to a problem? Please describe.
Several tickets exist that query how to display lengthy strings inside the debugger frame.
These tickets are all locked, more recently with a comment similar to "dlv-dap doesn't support this yet".
Describe the solution you'd like
Document the approach a user is supposed to take to view truncated long strings.
Describe alternatives you've considered
Add this feature to dlv-dap. This seems like a lot of work for something that can be covered in the short term with documentation.
Additional context
Yes, there is probably an article or note somewhere that explains this, but if it doesn't appear in the top ten when searching Google it essentially does not exist to the average programmer.
The text was updated successfully, but these errors were encountered: