search

slucky31 / mycomicsmanager

MIT License
1 stars 0 forks source link

fix(deps): update dependency fluentassertions to 6.12.1 (main) #683

Closed renovate[bot] closed 1 month ago

renovate[bot] commented 1 month ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
FluentAssertions (source) 6.12.0 -> 6.12.1 age adoption passing confidence

Release Notes

fluentassertions/fluentassertions (FluentAssertions) ### [`v6.12.1`](https://redirect.github.com/fluentassertions/fluentassertions/releases/tag/6.12.1) [Compare Source](https://redirect.github.com/fluentassertions/fluentassertions/compare/6.12.0...6.12.1) #### What's Changed ##### Improvements - Improve `BeEmpty()` and `BeNullOrEmpty()` performance for `IEnumerable`, by materializing only the first item - [#​2530](https://redirect.github.com/fluentassertions/fluentassertions/pull/2530) ##### Fixes - Fixed formatting error when checking nullable `DateTimeOffset` with `BeWithin(...).Before(...)` - [#​2312](https://redirect.github.com/fluentassertions/fluentassertions/pull/2312) - `BeEquivalentTo` will now find and can map subject properties that are implemented through an explicitly-implemented interface - [#​2152](https://redirect.github.com/fluentassertions/fluentassertions/pull/2152) - Fixed that the `because` and `becauseArgs` were not passed down the equivalency tree - [#​2318](https://redirect.github.com/fluentassertions/fluentassertions/pull/2318) - `BeEquivalentTo` can again compare a non-generic `IDictionary` with a generic one - [#​2358](https://redirect.github.com/fluentassertions/fluentassertions/pull/2358) - Fixed that the `FormattingOptions` were not respected in inner `AssertionScope` - [#​2329](https://redirect.github.com/fluentassertions/fluentassertions/pull/2329) - Capitalize `true` and `false` in failure messages and make them formattable to a custom `BooleanFormatter` - [#​2390](https://redirect.github.com/fluentassertions/fluentassertions/pull/2390), [#​2393](https://redirect.github.com/fluentassertions/fluentassertions/pull/2393) - Improved the failure message for `NotBeOfType` when wrapped in an `AssertionScope` and the subject is null - [#​2399](https://redirect.github.com/fluentassertions/fluentassertions/pull/2399) - Improved the failure message for `BeWritable`/`BeReadable` when wrapped in an `AssertionScope` and the subject is read-only/write-only - [#​2399](https://redirect.github.com/fluentassertions/fluentassertions/pull/2399) - Improved the failure message for `ThrowExactly[Async]` when wrapped in an `AssertionScope` and no exception is thrown - [#​2398](https://redirect.github.com/fluentassertions/fluentassertions/pull/2398) - Improved the failure message for `[Not]HaveExplicitProperty` when wrapped in an `AssertionScope` and not implementing the interface - [#​2403](https://redirect.github.com/fluentassertions/fluentassertions/pull/2403) - Improved the failure message for `[Not]HaveExplicitMethod` when wrapped in an `AssertionScope` and not implementing the interface - [#​2403](https://redirect.github.com/fluentassertions/fluentassertions/pull/2403) - Changed `BeEquivalentTo` to exclude `private protected` members from the comparison - [#​2417](https://redirect.github.com/fluentassertions/fluentassertions/pull/2417) - Fixed using `BeEquivalentTo` on an empty `ArraySegment` - [#​2445](https://redirect.github.com/fluentassertions/fluentassertions/pull/2445), [#​2511](https://redirect.github.com/fluentassertions/fluentassertions/pull/2511) - `BeEquivalentTo` with a custom comparer can now handle null values - [#​2489](https://redirect.github.com/fluentassertions/fluentassertions/pull/2489) - Ensured that nested calls to `AssertionScope(context)` create a chained context - [#​2607](https://redirect.github.com/fluentassertions/fluentassertions/pull/2607) - One overload of the `AssertionScope` constructor would not create an actual scope associated with the thread - [#​2607](https://redirect.github.com/fluentassertions/fluentassertions/pull/2607) - Fixed `ThrowWithinAsync` not respecting `OperationCanceledException` - [#​2614](https://redirect.github.com/fluentassertions/fluentassertions/pull/2614) - Fixed using `BeEquivalentTo` with an `IEqualityComparer` targeting nullable types - [#​2648](https://redirect.github.com/fluentassertions/fluentassertions/pull/2648) **Full Changelog**: https://github.com/fluentassertions/fluentassertions/compare/6.12.0...6.12.1

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR was generated by Mend Renovate. View the repository job log.

coderabbitai[bot] commented 1 month ago

[!IMPORTANT]

Review skipped

Bot user detected.

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

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

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 using 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. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### 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.
codacy-production[bot] commented 1 month ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for f52c5b66542f6eaf9119e2b7c00cf3fec3fb9b96[^1] :white_check_mark: ∅ (target: 80.00%)
Coverage variation details | | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (f52c5b66542f6eaf9119e2b7c00cf3fec3fb9b96) | Report Missing | Report Missing | Report Missing | | | Head commit (2fbbe07cbc2a871cb3249863fbf5ac339bbd07ed) | 1789 | 1679 | 93.85% | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `
Diff coverage details | | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#683) | 0 | 0 | **∅ (not applicable)** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more [^1]: Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.