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
A number of times when we receive the issues we have to ask the user for the C# or O# log, the locations of these are not obvious to the users.
With the new "Issue Reporter" capability, we already investigated that O# log and C# are too large to be sent in the url payload, hence we can add commands that copy these logs to the clipboard, from which the user can directly paste the output.
The copying to clipboard capability is on vscode's plan for the October release- microsoft/vscode#217, once that is out we can leverage that.
The text was updated successfully, but these errors were encountered:
We can leverage the "logPath" in the extension context to put the o# and C# logs in a file from where the contents can direct;y be read when the need arises.
Thoughts @rchande ?
A number of times when we receive the issues we have to ask the user for the C# or O# log, the locations of these are not obvious to the users.
With the new "Issue Reporter" capability, we already investigated that O# log and C# are too large to be sent in the url payload, hence we can add commands that copy these logs to the clipboard, from which the user can directly paste the output.
The copying to clipboard capability is on vscode's plan for the October release- microsoft/vscode#217, once that is out we can leverage that.
The text was updated successfully, but these errors were encountered: