Support for SqlServer JSON Fields

[quisitive-crogers]

Added a common string -> IDataItem method
Added support for processing JSON data from SQL Query
Updated the Readme.md

[philnach]

@quisitive-crogers , can you take a look at the merge conflicts and then we can review your change?

[quisitive-crogers]

@quisitive-crogers , can you take a look at the merge conflicts and then we can review your change?

Done!

[philnach]

Thanks, I'll re-take a look at the PR later today.

[philnach]

Thanks for the fast turnaround and fixing the formatting.

[philnach]

@quisitive-crogers, looks like tests are failing with your change. Can you take a look?

You should be able to reproduce the failure by running: dotnet test --no-build --verbosity normal, you should also be able to run the "Build and Test all .NET..." action from your fork as well.

Here's the failure:

  Failed TestReadAsyncWithParameters [17 ms]
  Error Message:
   Test method Cosmos.DataTransfer.SqlServerExtension.UnitTests.SqlServerDataSourceExtensionTests.TestReadAsyncWithParameters threw exception: 
System.AggregateException: Configuration for SqlServerSourceSettings is invalid (Missing settings of type SqlServerSourceSettings) (The `ConnectionString` field is required.) (Either `QueryText` or `FilePath` are required!) ---> System.Exception: Missing settings of type SqlServerSourceSettings
  Stack Trace:
      at Cosmos.DataTransfer.Interfaces.ValidationExtensions.Validate[T](T settings) in /__w/data-migration-desktop-tool/data-migration-desktop-tool/Interfaces/Cosmos.DataTransfer.Interfaces/ValidationExtensions.cs:line 34
   at Cosmos.DataTransfer.SqlServerExtension.SqlServerDataSourceExtension.ReadAsync(IConfiguration config, ILogger logger, String queryText, DbParameter[] parameters, DbConnection connection, DbProviderFactory dbProviderFactory, CancellationToken cancellationToken)+MoveNext() in /__w/data-migration-desktop-tool/data-migration-desktop-tool/Extensions/SqlServer/Cosmos.DataTransfer.SqlServerExtension/SqlServerDataSourceExtension.cs:line 48
   at Cosmos.DataTransfer.SqlServerExtension.SqlServerDataSourceExtension.ReadAsync(IConfiguration config, ILogger logger, String queryText, DbParameter[] parameters, DbConnection connection, DbProviderFactory dbProviderFactory, CancellationToken cancellationToken)+MoveNext() in /__w/data-migration-desktop-tool/data-migration-desktop-tool/Extensions/SqlServer/Cosmos.DataTransfer.SqlServerExtension/SqlServerDataSourceExtension.cs:line 81
   at Cosmos.DataTransfer.SqlServerExtension.SqlServerDataSourceExtension.ReadAsync(IConfiguration config, ILogger logger, String queryText, DbParameter[] parameters, DbConnection connection, DbProviderFactory dbProviderFactory, CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
   at System.Linq.AsyncEnumerable.<TryGetFirst>g__Core|95_0[TSource](IAsyncEnumerable`1 source, CancellationToken cancellationToken) in /_/Ix.NET/Source/System.Linq.Async/System/Linq/Operators/FirstOrDefault.cs:line 130
   at System.Linq.AsyncEnumerable.<TryGetFirst>g__Core|95_0[TSource](IAsyncEnumerable`1 source, CancellationToken cancellationToken) in /_/Ix.NET/Source/System.Linq.Async/System/Linq/Operators/FirstOrDefault.cs:line 132
   at System.Linq.AsyncEnumerable.<FirstAsync>g__Core|87_0[TSource](IAsyncEnumerable`1 source, CancellationToken cancellationToken) in /_/Ix.NET/Source/System.Linq.Async/System/Linq/Operators/First.cs:line 31
   at Cosmos.DataTransfer.SqlServerExtension.UnitTests.SqlServerDataSourceExtensionTests.TestReadAsyncWithParameters() in /__w/data-migration-desktop-tool/data-migration-desktop-tool/Extensions/SqlServer/Cosmos.DataTransfer.SqlServerExtension.UnitTests/SqlServerDataSourceExtensionTests.cs:line 69

[quisitive-crogers]

@quisitive-crogers, looks like tests are failing with your change. Can you take a look?

Fixed. Not sure those are really appropriate as unit tests, but for the time being, I just got them working again.

[philnach]

Sorry, took me a bit to understand myself why it was failing. I see the break was because we are now validating the SqlServerExtensions settings. Good addition!