- Make sure we pass the error message string instead of an error object when we call `TelemetryProcessor.traceFailure` since TelemetryProcessor will call `JSON.stringify` on the error object which would result in an empty object
- Removed ErrorParserUtility since it only works on specific error types. We can just log the full error message and manually derive information we need from the message.
- Added option to include stack trace in `getErrorMessage`. This is useful for figuring out where the client side script errors are coming from.
- Some minor refactors
* 1) Updated mongo collection create pane to display a better error when a shard key is ill formed.
2) Updated an error message to use double quotes since no string interpolation is used. I thought it was included in a previoue PR but I guess the change didn't get staged.
* This fixes an issue where errors when editing documents in an API for MongoDB endpoint would not be presented in the UI.
* Changing null to undefined in several places
* Fixed style issue.
Unignored MongoProxyClient.ts from full lint
* More linter issues since the removal from lint ignore
Steve Faulkner
victor-meng
Srinath Narayanan
vchske
Tanuj Mittal
Laurent Nguyen