* Send message to Fabric when container is updated (via settings, created or deleted).
* Fix format
---------
Co-authored-by: Laurent Nguyen <languye@microsoft.com>
* Add vector index shard key
* npm run format
* rename shard key to vector index shard key
* add tooltip for quantization byte size
* change text for GSI and container in VectorEmbedding Policy
---------
Co-authored-by: Asier Isayas <aisayas@microsoft.com>
* Added throughput bucketing
* fix bugs
* enable/disable per autoscale selection
* Added logic
* change query bucket to group
* Updated to a tab
* Fixed unit tests
* Edit package-lock
* Compile build fix
* fix unit tests
* moving the throughput bucket flag to the client generation level
* Replaced monaco editor on Container Vector Policy tab with controls same as on create container ux
* Adds vector embedding policy to container management. Adds FullTextSearch to both add container and container management.
* Fixing unit tests and formatting issues
* More fixes
* Updating full text controls based on feedback
* Minor updates
* Editing test to fix compile issue
* Minor fix
* Adding paths for jest to ignore transform due to recent changes in upstream dependencies
* Adding mock to temporarily get unit tests to pass
* Hiding FTS feature behind the new EnableNoSQLFullTextSearch capability
* initial commit
* Add change partition key logic
* Update snapshot
* Update snapshot
* Update snapshot
* Update snapshot
* Cleanup code
* Disable Change on progress job
* add the database information in the panel
* add the database information in the panel
* clear in progress message and remove large partition key row
* hide from national cloud
* hide from national cloud
* Add check for public cloud
* Initial rough of keeping textfield blank. Still need to disable save button.
* Rough implementation with state moved up to settings component. Allows for discarding of new TTL when TTL is already enabled.
* Updating unit tests to include new display variable.
* Brought formatting back from master.
* Updating unit test snapshots.
* Ran prettier and renormalized modified files.
* Correct lint issues.
* Undo prettier changes to add collection code and testing snapshot.
* Restoring AddCollectionPanel to match master. Not modifying snapshot.
---------
Co-authored-by: Craig Boger <craig.boger@microsoft.com>
- 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
* Index refresh component introduced
- Made all notifications in Mongo Index editor have 12 font size
- Added indexing policy refresh to sql indexing policy editor
- Added "you have unsaved changes" message, replace old message for lazy indexing policy changes
* formatting changes
* addressed PR comments
- created `getErrorMessage` function which takes in an error string or any type of error object and returns the correct error message
- replaced `error.message` with `getErrorMessage` since `error` could be a string in some cases
- merged sendNotificationForError.ts with ErrorHandlingUtils.ts
- some minor refactoring
In part 2, I will make the following changes:
- Make `Logger.logError` function take an error message string instead of an error object. This will reduce some redundancy where the `getErrorMessage` function is being called twice (the error object passed by the caller is already an error message).
- Update every `TelemetryProcessor.traceFailure` call to make sure we pass in an error message instead of an error object since we stringify the data we send.
