mirror of
https://github.com/ckaczor/sqltoolsservice.git
synced 2026-02-16 10:58:30 -05:00
Add "Open XEL file" support to profiler in sqltoolsservice (#2091)
* Open XEL file changes * placeholders for openxel * add observable xe reader * md format tweaks * implement localfile as a new session type * add ErrorMessage to session stopped notice * fix flaky test * handle already running session * fix stopped session event send on file completion * fix flaky unit test * Update XElite and dependent versions * Fix errors after merge and remove failing tests for now * Fix main merge mess-up. Address comments. Add one more relevant test. * Remove extra namespace. * Remove unnecessary import * Fix build error * Address comments. * Remove disabiling JSON002 compiler warning * Address comments and update json handling * Fix build error * Fix integration test (emerged due to Main merge mess up) * Clean up code (no functional changes) --------- Co-authored-by: Karl Burtram <karlb@microsoft.com> Co-authored-by: shueybubbles <david.shiflet@microsoft.com>
This commit is contained in:
14
README.md
14
README.md
@@ -2,15 +2,19 @@
|
||||
[](https://mssqltools.visualstudio.com/CrossPlatBuildScripts/_build/latest?definitionId=379&branchName=main)
|
||||
|
||||
# Microsoft SQL Tools Service
|
||||
|
||||
The SQL Tools Service is an application that provides core functionality for various SQL Server tools. These features include the following:
|
||||
|
||||
* Connection management
|
||||
* Language Service support using VS Code protocol
|
||||
* Query execution and resultset management
|
||||
|
||||
# SQL Tools Service API Documentation
|
||||
|
||||
Please see the SQL Tools Service API documentation at https://microsoft.github.io/sqltoolssdk/.
|
||||
|
||||
# Setup, Building and Testing the codebase
|
||||
|
||||
Please see the SQL Tools Service wiki documentation at https://github.com/Microsoft/sqltoolsservice/wiki
|
||||
|
||||
# Contribution Guidelines
|
||||
@@ -104,13 +108,11 @@ so that your commits provide a good history of the changes you are making. To b
|
||||
|
||||
### Add Unit Tests for New Code
|
||||
|
||||
If you're adding a new feature to the project, please make sure to include adequate [xUnit](http://xunit.github.io/)
|
||||
tests with your change. In this project, we have chosen write out unit tests in a way that uses the
|
||||
actual PowerShell environment rather than extensive interface mocking. This allows us to be sure that
|
||||
our features will work in practice.
|
||||
If you're adding a new feature to the project, please make sure to include adequate [nUnit](http://nunit.org/)
|
||||
tests with your change.
|
||||
|
||||
We do both component-level and scenario-level testing depending on what code is being tested. We don't
|
||||
expect contributors to test every possible edge case. Testing mainline scenarios and the most common
|
||||
We do both component-level and scenario-level testing depending on what code is being tested. We don't
|
||||
expect contributors to test every possible edge case. Testing mainline scenarios and the most common
|
||||
failure scenarios is often good enough.
|
||||
|
||||
We are very happy to accept unit test contributions for any feature areas that are more error-prone than
|
||||
|
||||
Reference in New Issue
Block a user