logging:

[Josverl]

• log extension version at startup to ease error reporting
• convert logs , warning and errors to printable text Note: possibly may want to limit logging for errors , or send extended info only to debug log.
• specify type as log to allow for highlighting using any installed syntax highlighter for logs

[jakobrosenberg]

Love it!

Should the "what" precede the "where"?

Eg. should:

  if (data instanceof Error) {
    return data.stack || data.message;
  }

be

  // I'm leaning towards this one since the stack can be found in the developer console.
  if (data instanceof Error) {
    return data.message || data.stack;
  }

or

  if (data instanceof Error) {
    return [data.message, data.stack].filter(Boolean).join('\r\n');
  }

[Josverl]

makes sense, and I think it also makes sense to log the error to the log , but log all the details of the connection / failure using log.debug so that can be hidden / revealed by changing the log level.

[jakobrosenberg]

Yes, I've been meaning to revise the logging levels and coverage, but the priority hasn't been high so far.

[jakobrosenberg]

:tada: This PR is included in version 2.8.7 :tada:

The release is available on:

• Visual Studio Marketplace
• GitHub release

Your semantic-release bot :package::rocket: