search

Gigas002 / GTiff2Tiles

Analogue of gdal2tiles.py/MapTiler on C#.
https://gigas002.github.io/GTiff2Tiles/
Do What The F*ck You Want To Public License
15 stars 4 forks source link

Bump NUnit.Analyzers from 3.10.0 to 4.0.0 #286

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 9 months ago

Bumps NUnit.Analyzers from 3.10.0 to 4.0.0.

Release notes

Sourced from NUnit.Analyzers's releases.

NUnit Analyzers 4.0 - January 27, 2024

Version 4 of the NUnit analyzers drops the support for older releases of Visual Studio. I.e. releases of Visual Studio that are older than Visual Studio 2019 16.3. In addition, this release contains various bug fixes to existing analyzers, support of the CancelAfterAttribute that was introduced in NUnit 4, and extends the codefix for NUnit2007 to also work when .Within is used.

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

Issues Resolved

Features and Enhancements

  • #669 NUnit2007 does not provide codefix when .Within is used
  • #609 Drop support for VS before 2019

Bugs

  • #663 NUnit1027 fired when CancellationToken and [CancelAfter] is given
  • #659 NUnit1032 throws an exception in a specific configuration
  • #656 NUnit1028 warns about overridden methods
  • #635 ArgumentException in DisposeFieldsAndPropertiesInTearDownAnalyzer

Tooling, Process, and Documentation

  • #676 chore: markdownlint-cli2-config is removed use flag instead
  • #668 chore(deps): Bump StyleCop.Analyzers.Unstable from 1.2.0.507 to 1.2.0.556
  • #662 chore: Bump NUnit 4 to version 4.0.1
  • #660 chore: Bump to NUnit 4
  • #654 chore: Bump version
  • #630 Update NUnit Analyzer docs to respect 120-character docs rule documentation
  • #508 Restore "File version" and "Product version" in analyzer dlls
Changelog

Sourced from NUnit.Analyzers's changelog.

NUnit Analyzers 4.0 - January 27, 2024

Version 4 of the NUnit analyzers drops the support for older releases of Visual Studio. I.e. releases of Visual Studio that are older than Visual Studio 2019 16.3. In addition, this release contains various bug fixes to existing analyzers, support of the CancelAfterAttribute that was introduced in NUnit 4, and extends the codefix for NUnit2007 to also work when .Within is used.

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

  • Abrynos
  • gfoidl
  • Laniusexcubitor
  • MaceWindu
  • manfred-brands
  • mikkelbu
  • RenderMichael
  • SeanKilleen

Issues Resolved

Features and Enhancements

  • #669 NUnit2007 does not provide codefix when .Within is used
  • #609 Drop support for VS before 2019

Bugs

  • #663 NUnit1027 fired when CancellationToken and [CancelAfter] is given
  • #659 NUnit1032 throws an exception in a specific configuration
  • #656 NUnit1028 warns about overridden methods
  • #635 ArgumentException in DisposeFieldsAndPropertiesInTearDownAnalyzer

Tooling, Process, and Documentation

  • #676 chore: markdownlint-cli2-config is removed use flag instead
  • #668 chore(deps): Bump StyleCop.Analyzers.Unstable from 1.2.0.507 to 1.2.0.556
  • #662 chore: Bump NUnit 4 to version 4.0.1
  • #660 chore: Bump to NUnit 4
  • #654 chore: Bump version
  • #630 Update NUnit Analyzer docs to respect 120-character docs rule documentation
  • #508 Restore "File version" and "Product version" in analyzer dlls

NUnit Analyzers 3.10 (and 2.10) - November 27, 2023

This release adds a couple of improvements to the analyzers:

  • Check that users don't accidentally specify CallerArgumentExpression parameters
  • Relax analyzers for added support for IAsyncEnumerable on *Source attributes

These improvements extend the functionality in the beta that added support for NUnit 4 and for migrating to NUnit 4.

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

... (truncated)

Commits
  • bb132f0 Merge pull request #682 from nunit/release4.0
  • 7056b7f chore: Update release notes
  • 87e452f Merge pull request #680 from nunit/chore/keep-version-information
  • c060984 chore: Keep version in resulting dll
  • b0655fe Merge pull request #678 from manfred-brands/issue663_CancellationToken
  • 70dd521 Add support for CancelAfter on TestFixture class
  • bb0263c Code Review changes
  • 053e2a1 Update build.cake to test against both NUnit 3 and 4
  • f2d269c Fix tests for NUnit 3.x build
  • 88aeaa8 Update Test method parameter checks to account for CancellationToken
  • 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)
coderabbitai[bot] commented 9 months ago

[!IMPORTANT]

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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: - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit-tests for this file.` - 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 tests 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 from git and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit tests.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` 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 a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - The JSON schema for the configuration file is available [here](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - 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/coderabbit-overrides.v2.json` ### CodeRabbit Discord Community Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback.
codecov[bot] commented 9 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (bc7c8bc) 80.73% compared to head (fc1f374) 80.73%.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #286 +/- ## ======================================= Coverage 80.73% 80.73% ======================================= Files 31 31 Lines 1142 1142 Branches 300 300 ======================================= Hits 922 922 Misses 191 191 Partials 29 29 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.