-
Notifications
You must be signed in to change notification settings - Fork 289
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
Merge more methods from TdsParserStateObject #1843
Conversation
…would maybe help to start working on fix the async bug.
Codecov ReportBase: 69.19% // Head: 70.21% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1843 +/- ##
==========================================
+ Coverage 69.19% 70.21% +1.01%
==========================================
Files 292 292
Lines 61727 61399 -328
==========================================
+ Hits 42713 43109 +396
+ Misses 19014 18290 -724
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
/Azurepipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@bhugot @JRahnama as I hinted in #1520 (comment) I have also merged about 2000 more lines of this file. I was actually about to make a PR about it right now. I can't review this at the moment, but at a glance it looks like you have made changes to more files than I did, but I have merged a little bit more of the TdsParserStateObject file. My version splits the merge in smaller commits too. So, I will make the PR and leave it up to you to decide what to do with it. |
@bhugot my bad, I should have added a link to it at least. Anyway, I was trying to compare your version to mine, but it isn't so easy. It looks like we have a different position/order for some methods, which messes up the diff viewer. But I can see we have merged some different parts of the file (e.g. you have merged more snapshot related methods, but still I have merged more code in total). We could merge both our versions, but since these PRs are already huge, it is probably best to go for a third PR along with the rest of the file. The important methods for fixing the async bug are already merged by both PRs anyway. Thanks for the feedback on my PR by the way, I will check the code and come back with answers later. PS: if you are working on TdsParser, I would say consider making smaller commits. I don't know what the reviewers prefer, but personally, I found it a bit hard to follow the first commit of this PR. Also try to keep the same order for the methods. |
more merge after #1520 It would maybe help to start working on fix the async bug.
I think we should be able to do more.