Improved SSDT .sql script discovery: SsdtPath can now point to a .sqlproj project file and will get paths to all .sql scripts marked as Build.
SsdtPath can still be set to a root folder instead, but now it is not reliant on subfolder conventions; instead, it will recursively search for .sql files under the given SsdtPath and analyze them to determine script type.
Added support (or at least basic support) for stored procs
Fixed a bug in the view parser where aliased columns were using the referenced table column name
If a .sql file fails parsing for any reason, the file name will be displayed to user when they hover over the type provider to help with troubleshooting.
Updated SSDT docs
Types of changes
What types of changes does your code introduce to SQLProvider?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Adding .sqlproj support for SsdtPath is a non-breaking new feature.
Changing SsdtPath behavior when set to a folder path to recursively scan for .sql files and auto-analyzing their types (table, view, sproc) is potentially breaking change since previously it didn't analyze scripts and expected convention based folders.
I think it's a minor risk though.
New feature is implementation of sprocs
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[ ] Build and tests pass locally
[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have added necessary documentation (if appropriate)
Further comments
I don't think I have added my SSDT test project to the test sln yet for the build script to execute. I'll try to remember to do that next time.
Thorium
commented
3 years ago
Proposed Changes
SsdtPathcan now point to a.sqlprojproject file and will get paths to all .sql scripts marked as Build.SsdtPathcan still be set to a root folder instead, but now it is not reliant on subfolder conventions; instead, it will recursively search for .sql files under the givenSsdtPathand analyze them to determine script type.Types of changes
What types of changes does your code introduce to SQLProvider? Put an
xin the boxes that apply[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Adding .sqlproj support for SsdtPath is a non-breaking new feature.
Changing SsdtPath behavior when set to a folder path to recursively scan for .sql files and auto-analyzing their types (table, view, sproc) is potentially breaking change since previously it didn't analyze scripts and expected convention based folders. I think it's a minor risk though.
New feature is implementation of sprocs
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
I don't think I have added my SSDT test project to the test sln yet for the build script to execute. I'll try to remember to do that next time.