search

madhon / catalogjwt

Catalog API with JWT Auth Sample
0 stars 0 forks source link

build(deps): bump Riok.Mapperly from 3.2.0 to 3.3.0 #339

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps Riok.Mapperly from 3.2.0 to 3.3.0.

Release notes

Sourced from Riok.Mapperly's releases.

v3.3.0

3.3.0 (2023-12-12)

Bug Fixes

  • escape method parameters with reserved keywords (#756) (8f7528a)
  • extension method parameters for existing target mappings (#923) (86408ce)
  • improve location of reported diagnostics (#937) (980ac3e)
  • obsolete constructors should have the last priority whlie matching constructors (regression) (#898) (20b7da6)
  • remove unnecessary null conditional access in conditions of property mappings (#788) (c4eed62)
  • resolve correct mapper defaults for roslyn versions <= 4.4 (#958) (14a4ed3)
  • Respect AllowNullPropertyAssignment correctly when mapping code is not a direct assignment (#939) (cac2f2e)
  • when resolving constructors allow a non-nullable value type to be assigned to a nullable value type (#938) (6e08f8e)

Features

  • add diagnostic for nested ignores (#818) (0f61698)
  • add IncludedMembers configuration option and support private member mapping (c0ed6eb)
  • Add option to specify the format provider or culture of a property (#929) (42d3e26)
  • Add option to specify the string format of a property (#921) (236a46f)
  • add strict mapping (#700) (9d6c21a)
  • case-insensitive MapProperty configurations matching for constructor parameters (#957) (b9db799)
  • fix incorrect private set when ~MemberVisibility.Accessible is used (#933) (b60441a)
  • improve ToString handling and use simplest overloads available (#950) (574cef7)
  • support derived type mappings for existing target objects (918f59d)
  • support static mapping methods in non-static mappers (#681) (1724124)
  • use IEnumerable Dictionary constructor for synthetic mappings (#755) (1bc7bdd)

v3.3.0-next.6

3.3.0-next.6 (2023-12-06)

Bug Fixes

  • resolve correct mapper defaults for roslyn versions <= 4.4 (#958) (14a4ed3)

Features

  • case-insensitive MapProperty configurations matching for constructor parameters (#957) (b9db799)
  • support derived type mappings for existing target objects (918f59d)

v3.3.0-next.5

3.3.0-next.5 (2023-11-28)

Bug Fixes

... (truncated)

Commits
  • 73d1c71 chore: remove unneeded configure pages action (#980)
  • b9db799 feat: case-insensitive MapProperty configurations matching for constructor pa...
  • cec43ad chore(deps): Bump actions/setup-dotnet from 3 to 4 (#973)
  • 14a4ed3 fix: resolve correct mapper defaults for roslyn versions <= 4.4 (#958)
  • 918f59d feat: support derived type mappings for existing target objects
  • 35aea49 chore(deps): Bump csharpier from 0.26.3 to 0.26.4 (#971)
  • 7628cf3 chore: fix integration tests (#961)
  • 997b043 chore: increase threshold since benchmark tests have higher volatility lately...
  • 6cfdb91 chore: upgrade docusaurus (#967)
  • e7ed285 chore(deps-dev): Bump @​docusaurus/eslint-plugin in /docs (#966)
  • 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)

This change is Reviewable

pull-request-quantifier-deprecated[bot] commented 11 months ago

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .props : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

dependabot[bot] commented 11 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.