-
Notifications
You must be signed in to change notification settings - Fork 7
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
Gh 30 call info analyzer #33
Conversation
Pull Request Test Coverage Report for Build pc6jvryfri5oacdr
💛 - Coveralls |
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.
👍
The Roslyn stuff is still mysterious magic for me, so I'm probably not going to be able to provide much more than a sanity check for these. If there's anything in particular you want feedback on in terms of design please let me know in the PR description so I can focus on those parts. :)
Hi @dtchepak I think that as usual, I would need a feedback about diagnostic messages presented to the users - I took all of the messages from NSubstitute exceptions but maybe we can do better. Additionally, if you know any other misusages of callInfo let me know so I can extend the logic of analyzer. When it comes to design, this analyzer is a bit complex so if you see any way to simplify/refactor feel free to ping me |
Closes #30