-
Notifications
You must be signed in to change notification settings - Fork 15
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
Regression: NullReferenceException thrown when argument customization is not provided. #6
Comments
Hi the stacktrace is below:
|
I haven't had a chance to pull it down and check and am not at a computer, but at first glance it looks like the null check needs to happen in |
whoops.. posted stack trace info in wrong issue... Settings:
Stack trace:
If I remove the comment for the ArgumentCustomization setting, it works just fine (as mentioned earlier in thread). |
Hi there, Took me awhile to get to the bottom of this. It seems while making the change for #5 I managed to somehow get a tag on a version of code that doesn't exist but got pushed remote and overwritten after a bad merge. This code got pushed to nuget and only had half of my actual changes. The odd phantom commit can be found here. Since i use git versioning to determine my scheme i've bumped the version to 1.3 to make sure people should pull the new version however it has no actual new changes but should fix this regression. Hopefully that makes some sense, please report back if you have any issues or just to confirm it's fixed. Thanks, |
All seems good now @Romanx thanks for the very quick fix 👍 |
You're more than welcome, thanks for the report. |
Seems to surface like #3 although could be something different.
The text was updated successfully, but these errors were encountered: