-
-
Notifications
You must be signed in to change notification settings - Fork 981
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
Fixed: Add validation warning for sealed classes containing benchmarks #2660
Conversation
ketanpkolte
commented
Oct 26, 2024
- Added compilation error handling for non-public classes.
- Added Test for new compilation error handling
- Removed assertion for private classes and included it in compilation error handling.
tests/BenchmarkDotNet.Tests/Validators/CompilationValidatorTests.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Tim Cassell <35501420+timcassell@users.noreply.github.com>
Update src/BenchmarkDotNet/Validators/CompilationValidator.cs Co-authored-by: Tim Cassell <35501420+timcassell@users.noreply.github.com> Added tests for Protected and Internal + cleanup corrected syntax in message added individual messages for validation and Tests Added validation for sealed, notpublic, generic and IsRunnableGenericType
Update Master branch
Can you help regarding the commits. |
Don't worry about squash or rebase. Merging from upstream was good enough. But you should keep your fork's master branch up to date with upstream, and always create a branch for your work. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork |
Co-authored-by: Tim Cassell <35501420+timcassell@users.noreply.github.com>
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.
Thanks!