-
Notifications
You must be signed in to change notification settings - Fork 44
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
Update verify #151
Update verify #151
Conversation
@gasparnagy so we had this debate on what is a breaking change and what is not. Do I need to change the changelog to feature improvement or...? |
@ajeckmans Please wait, I wanted to double check if my assumption really works. |
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.
Please see my minor comments.
....Verify.ReqnrollPlugin.IntegrationTest/Reqnroll.Verify.ReqnrollPlugin.IntegrationTest.csproj
Outdated
Show resolved
Hide resolved
....Verify.ReqnrollPlugin.IntegrationTest/Reqnroll.Verify.ReqnrollPlugin.IntegrationTest.csproj
Show resolved
Hide resolved
Plugins/Reqnroll.Verify/Reqnroll.Verify.ReqnrollPlugin/Reqnroll.Verify.ReqnrollPlugin.csproj
Outdated
Show resolved
Hide resolved
Plugins/Reqnroll.Verify/Reqnroll.Verify.ReqnrollPlugin/build/Reqnroll.Verify.targets
Outdated
Show resolved
Hide resolved
Plugins/Reqnroll.Verify/Reqnroll.Verify.ReqnrollPlugin/build/Reqnroll.Verify.props
Outdated
Show resolved
Hide resolved
…he generator was not needed anymore, so it is removed as well.
…ugin Cleaned Reqnroll.Verify.ReqnrollPlugin.csproj to be more consistent with the other plugin project files Fixed wrong tags in Reqnroll.Verify.nuspec
@gasparnagy can you check again? |
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.
Small changes requested. I haven't done a manual check this time, please make sure you try it.
Side note: For me it is better if you do not apply rebase or force push after an initial review has been done, because this way I have to make a full review again and I cannot just see the "diff". Merging the main to the PR branch is fine - we will squash it anyway.
Plugins/Reqnroll.Verify/Reqnroll.Verify.ReqnrollPlugin/Reqnroll.Verify.ReqnrollPlugin.csproj
Outdated
Show resolved
Hide resolved
@gasparnagy I checked the local produced nuget package in an existing real world project and it is working fine. |
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.
Thx!
This reverts commit dd7ecf6.
@ajeckmans Sorry, I forgot that we should not merge this before v2.0.3. I'm undoing it now. |
* main: Reqnroll.Verify: Support for Verify v24 (Verify.Xunit v24.2.0) for .NET 4.7.2+ and .NET 6.0+. (#151, #170) use pull_request_template.md from the .github repo Fix spelling mistake in CONTRIBUTING.md Bump version fix config docs Add release contributors to CHANGELOG (#171) Update CONTRIBUTING with "draft PR" workflow and no force push after review fix CHANGELOG Fix project template binding (#169)
Updates the Reqnroll.Verify plugin to work with the latest Verify release 24.2.0.
With this change the plugin also does not need to be a generator plugin anymore, but just a runtime plugin.
Types of changes
Checklist: