-
Notifications
You must be signed in to change notification settings - Fork 315
Merge | Merge TdsParserStateObject, cleanup TdsParser files #3647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Excited to get this one merged, but conflicts need addressing first :( (and they were probably caused by me anyhow...) |
Thanks - it looks like TdsParserStateObject had one instance of missing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting so close!
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks for this heavy lifting
The CI errors appear to be transient, so I'll babysit this until it's green. |
Description
TdsParserStateObject currently comprises two target-specific files which have X differences:
All of the other methods in TdsParserStateObject.netfx.cs and .netcore.cs are identical. I've thus merged them into the shared TdsParserStateObject.cs file in one PR; this does make it a little larger, but it's hopefully easy enough to review.
This also mops up the trailing TdsParser.SSPI.cs file, which only have a few methods but was large enough that I didn't want to deal with it as part of the large TdsParser.cs merge.
Finally, there were a handful of now-unnecessary .stub.cs files, which I've pruned.
Each commit moves one or two methods for ease of review.
Issues
Relates to #1261.
Testing
Automated tests pass, could someone run CI please?