Bump FastEndpoints.Swagger from 5.5.0 to 5.8.1

[dependabot]

Bumps FastEndpoints.Swagger from 5.5.0 to 5.8.1.

Release notes

Sourced from FastEndpoints.Swagger's releases.

v5.8.1 Release

IMPROVEMENTS

• optional boolean argument urlEncoded for AllowFormData() method to accept application/x-www-form-urlencoded instead of multipart/form-data #info
• ability to submit a request DTO as multipart form data when integration testing endpoints that accept form data. #409
• ability to execute a non-concrete ICommand types #411
• refactor & simplify httpclient extensions for testing

FIXES

• EndpointWithMapping<TRequest, TResponse, TEntity> map methods becoming protected in v5.8 #info
• double response issue if pre-processor sent response and validator also has failures. #info
• endpoint factory being inferred from request body issue #info
• incorrect swagger spec generation issue #info
• minor oversight in accept metadata checking/caching per endpoint on first request #info

v5.8 Release

NEW

• support for record types and required keyword by removing new() constraint on request DTOs
• allow command handlers to manipulate endpoint validation state #info
• ability to share state between pre/post processors and endpoint handler #info
• add Policy() method to endpoint class for building authorization requirements per endpoint #info
• ability to automatically add produces 400 metadata for endpoints with validators #info
• ability to remove optional [FromHeaders],[FromClaim],[HasPermission] annotated properties from swagger request schema #387
• support for IParsable<T> interface from .net 7.0 #385
• support for ignoring GET request DTO properties annotated with [JsonIgnore] attribute for disabling binding #info

IMPROVEMENTS

• better swagger support for OAS2.0 #390
• testing extensions now return a TestResult<TResponse> record instead of a value tuple
• optimize the endpoint request handler internals

FIXES

• duplicate validator detection issue #394
• contention issue with parallel test runs #395
• RSA instance being disposed when using Assymetric JWT signing style
• handling of STJ exceptions when the error is not directly related to any field of the json payload #391

v5.7.2 Release

IMPROVEMENTS

• add overload for TagDescriptions() method for adding swagger tag descriptions with tuples #info
• swagger support for route params with mixed patterns #380
• misc. improvements to FastEndpoints.Security package internals
• upgrade all dependencies to latest

v5.7.1 Release

FIXES

• .net 7 IEndpointFilter classes not executing correctly #info
• object disposed exeception when signing with assymetric key #372
• STJ trying to bind json object as IEnumerable when dto prop is IDictionary #info

v5.7 Release

... (truncated)

Commits

• 24840cc v5.8.1 release
• afde256 accept url encoded form data #414
• 93985ee bump version
• cde7286 #411 Execute non-concrete command type (#413)
• a9cd2aa remove null coalescing operator
• c933bee fix accept metadata checking
• 8d818f9 bump version
• 0d9c742 update test snapshots
• de176fc fix incorrent swagger spec gen for request parameters
• be15324 bump version
• Additional commits viewable in compare view

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 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)

[pull-request-quantifier-deprecated]

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.

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
  • 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 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? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[github-advanced-security]

You have successfully added a new CodeQL configuration .github/workflows/codeql-analysis.yml:analyze. As part of the setup process, we have scanned this repository and found 33 existing alerts. Please check the repository Security tab to see all alerts.

[dependabot]

Superseded by #32.