New-DbaConnectionStringBuilder, param reorganization #9613
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
tear it UP! 🔥 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Invoke-ManualPester)Purpose
Make New-DbaConnectionStringBuilder a little more precise. The idea should be that whatever is in the initial connectionstring is preserved UNLESS specifically passed down.
Approach
Using Test-Bound where appropriate and ShouldSerialize, preserving all the behaviour but fixing overrides
Commands to test
Added a ton of tests, converted pester3 syntax to pester4 (waiting for aider-related to convert to pester5 automagically) coverage is now 100%, shouldn't ever regress ^_^
Screenshots