search

Gigas002 / dotnet_gh_deploy

This is project description! Yes it is!
https://gigas002.github.io/dotnet_gh_deploy/
GNU General Public License v3.0
0 stars 0 forks source link

Bump NUnit.Analyzers from 4.2.0 to 4.3.0 #224

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps NUnit.Analyzers from 4.2.0 to 4.3.0.

Release notes

Sourced from NUnit.Analyzers's releases.

NUnit Analyzers 4.3 - August 9, 2024

This release of the NUnit Analyzers contains some bug fixes to existing analyzers and code fixes - among other improvements to trivia when using the code fix of NUnit2049.

For new features we now warn against using TestContext.Write as this will be obsolete in NUnit at some point; NUnit1001 now recognises and check generic TestCase attributes; and we have added a new analyzer and code fix for simplifying usages of ValuesAttribute.

The release contains contributions from the following users (in alphabetical order):

Issues Resolved

Features and Enhancements

  • #770 Add rule to detect calls to TestContext.Write methods and CodeFix to replace usages with Out.Write
  • #767 Augment NUnit1001 to recognized and check generic TestCase attributes
  • #755 New diagnostic: The Values attribute can be simplified.

Bugs

  • #766 Error when TearDown method is defined in partial test classes - Syntax node is not within syntax tree
  • #743 NUnit1032 (missing Dispose), if dispose is wrapped in "(… as IDisposable)?.Dispose()"
  • #739 Null suppression does not work when Assert is fully qualified
  • #713 Code fix for NUnit2049 places the comma at a wrong place and messes up indentation bug

Tooling, Process, and Documentation

  • #764 Update the solution file
  • #761 Update nunit.analyzers.nuspec to specify that NUnit.Analyzers v4 is intended to be used with NUnit 4.
  • #756 error NUnit1032 is incorrect when InstancePerTestCase and constructor is used to initialize IDisposible
  • #741 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0 in /src
  • #737 Update NUnit2013.md to fix code block
  • #736 chore: bump version
  • #734 Why dropping composite message formatting support also for Assert.Pass/Fail/... where there are no actual and constraint parameters?
Changelog

Sourced from NUnit.Analyzers's changelog.

# NUnit Analyzers 4.3 - August 9, 2024

This release of the NUnit Analyzers contains some bug fixes to existing analyzers and code fixes - among other improvements to trivia when using the code fix of NUnit2049.

For new features we now warn against using TestContext.Write as this will be obsolete in NUnit at some point; NUnit1001 now recognises and check generic TestCase attributes; and we have added a new analyzer and code fix for simplifying usages of ValuesAttribute.

The release contains contributions from the following users (in alphabetical order):

Issues Resolved

Features and Enhancements

  • #770 Add rule to detect calls to TestContext.Write methods and CodeFix to replace usages with Out.Write
  • #767 Augment NUnit1001 to recognized and check generic TestCase attributes
  • #755 New diagnostic: The Values attribute can be simplified.

Bugs

  • #766 Error when TearDown method is defined in partial test classes - Syntax node is not within syntax tree
  • #743 NUnit1032 (missing Dispose), if dispose is wrapped in "(… as IDisposable)?.Dispose()"
  • #739 Null suppression does not work when Assert is fully qualified
  • #713 Code fix for NUnit2049 places the comma at a wrong place and messes up indentation bug

Tooling, Process, and Documentation

  • #764 Update the solution file
  • #761 Update nunit.analyzers.nuspec to specify that NUnit.Analyzers v4 is intended to be used with NUnit 4.
  • #756 error NUnit1032 is incorrect when InstancePerTestCase and constructor is used to initialize IDisposible
  • #741 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0 in /src
  • #737 Update NUnit2013.md to fix code block
  • #736 chore: bump version
  • #734 Why dropping composite message formatting support also for Assert.Pass/Fail/... where there are no actual and constraint parameters?

NUnit Analyzers 4.2 - April 24, 2024

This release of the Analyzers extends NUnit2050 to also cover Assume and Nunit1032 to consider dispose of a type having explicit interface implementation. Furthermore, named parameters are now handled correctly codefixes for classical asserts, and NUnit2010 improves the logic for determining Equals methods.

... (truncated)

Commits
  • 52a0670 Merge pull request #775 from nunit/release4.3
  • cf27270 chore: Update release notes
  • b59c564 Merge pull request #772 from manfred-brands/Issue770_TestContext.Write
  • bf26b78 Fix linting error
  • 9501ab8 Code review changes
  • a00035e Merge pull request #773 from manfred-brands/Issue767_GenericTestCase
  • ab3d365 Merge pull request #754 from Bartleby2718/713-NUnit2049-indentation
  • 48bf08f Merge pull request #774 from manfred-brands/Issue766_PartialTestClasses
  • 7c96200 Field is only needed for NUNIT4 tests
  • f017e6d C#11 is not available for .NET6.0
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

coderabbitai[bot] commented 1 month ago

Walkthrough

The recent changes involve updating the NUnit.Analyzers package reference from version 4.2.0 to 4.3.0 in multiple project files. This upgrade aims to enhance the static analysis capabilities related to NUnit tests, incorporating improvements, bug fixes, and potentially new features. Overall, the structure and functionality of the projects remain intact.

Changes

File Change Summary
Deploy.Server.Tests/Deploy.Server.Tests.csproj
Deploy.Tests/Deploy.Tests.csproj		 Updated NUnit.Analyzers from version 4.2.0 to 4.3.0.

Poem

🐇 In the meadow where tests do play,
A hop of change has come our way!
With analyzers fresh and bright,
Our code will shine with pure delight.
Version bumps, a joyful cheer,
Let's code and test without a fear! 🌼✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.