Bump the swashbuckle group with 3 updates#36
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps MicroElements.Swashbuckle.FluentValidation from 7.1.2 to 7.1.6 Bumps Swashbuckle.AspNetCore from 10.1.2 to 10.2.1 Bumps swashbuckle.aspnetcore.cli from 10.1.2 to 10.2.1 --- updated-dependencies: - dependency-name: MicroElements.Swashbuckle.FluentValidation dependency-version: 7.1.6 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: swashbuckle - dependency-name: Swashbuckle.AspNetCore dependency-version: 10.2.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: swashbuckle - dependency-name: swashbuckle.aspnetcore.cli dependency-version: 10.2.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: swashbuckle ... Signed-off-by: dependabot[bot] <support@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated MicroElements.Swashbuckle.FluentValidation from 7.1.2 to 7.1.6.
Release notes
Sourced from MicroElements.Swashbuckle.FluentValidation's releases.
7.1.6
Stable 7.1.6 (supersedes the unreleased 7.1.5 betas).
Changes
$refreplaced with an inline copy (and the child component left orphaned) when a nested object's constraints come fromChildRulesor an inline child validator (#198, #206).$refs, but when the nested type had no standalone validator its component schema gained itsrequiredonly after the parent's inline snapshot — the stalerequireddiverged and defeated the restore check. TheRequiredcomparison inHasValidationConstraintChangesis now directional.SetValidator(with a standalone child validator) was already correct;BigInteger/enum per-model constraints (#146/#176) continue to work.ConditionalRulesModeoption to control how.When()/.Unless()conditional rules are handled (Exclude(default) /Include/IncludeWithWarning) (#203)..Matches()rules on one property rendered incorrectly (only the first pattern shown). They are now combined into a singlepatternvia lookahead assertions, across Swashbuckle,MicroElements.AspNetCore.OpenApi.FluentValidation, and NSwag (#204, #205).SchemaGenerationOptions.UseAllOfForMultipleRulestrue→false; set it totrueto keep the legacyallOfrepresentation.NuGet: https://www.nuget.org/packages/MicroElements.Swashbuckle.FluentValidation/7.1.6
7.1.6-beta.1
Pre-release for the upcoming 7.1.6.
Changes since 7.1.5-beta.2
$refstill replaced with an inline copy (and the child component left orphaned) when nested object constraints come fromChildRulesor an inline child validator (#198, #206).$refs, but when the nested type has no standalone validator its component schema gains itsrequiredonly after the parent's inline snapshot is taken, so the stalerequireddiverged and defeated the restore check — leaving an inline copy and an orphaned component.Requiredcomparison inHasValidationConstraintChangesis now directional — restoration is only blocked when the inline copy carries a required entry the component lacks.SetValidator(with a standalone child validator) was already correct;BigInteger/enum per-model constraints (#146/#176) continue to work.NuGet: https://www.nuget.org/packages/MicroElements.Swashbuckle.FluentValidation/7.1.6-beta.1
7.1.5-beta.2
Pre-release for the upcoming 7.1.5.
Changes since 7.1.5-beta
.Matches()rules on one property displayed incorrectly — only the first pattern shown, property duplicated (#204, #205).allOfsubschemas, which Swagger UI/Redoc/Scalar collapse, keeping only the firstpattern..Matches()rules are combined into a singlepatternvia lookahead assertions, preserving.Matches()semantics and rendering correctly.MicroElements.AspNetCore.OpenApi.FluentValidation, and NSwag.SchemaGenerationOptions.UseAllOfForMultipleRulesdefaulttrue→false; set it totrueto keep the legacyallOfrepresentation.Already in 7.1.5-beta
ConditionalRulesModeoption to control how.When()/.Unless()conditional rules are handled during schema generation (#203).See CHANGELOG.md for full details.
7.1.5-beta
What's New
ConditionalRulesModeoption (Issue #203)Controls how conditional validation rules (
.When(),.Unless()) are handled during OpenAPI schema generation.Modes:
Exclude(default) — conditional rules are excluded from schema (backward-compatible)Include— conditional rules are included in schemaIncludeWithWarning— same as Include, but logs a warning for each conditional ruleUsage:
Why: When users write
.When(x => x.Prop is not null)as a null-guard, validation constraints (minLength, maxLength, etc.) were silently dropped from the schema. This option lets users opt-in to including those constraints.7.1.4
Changes in 7.1.4
FluentValidationOperationTransformer(IOpenApiOperationTransformer) forMicroElements.AspNetCore.OpenApi.FluentValidation(Issue #200)[AsParameters]now receive validation constraints (min/max, required, pattern, etc.)[AsParameters]AddFluentValidationRules()FluentValidationSchemaTransformerskipped all property-level schemas, but for nested object types this was the only transformer call7.1.4-beta
Changes in 7.1.4-beta
FluentValidationOperationTransformer(IOpenApiOperationTransformer) forMicroElements.AspNetCore.OpenApi.FluentValidation(Issue #200)[AsParameters]now receive validation constraints (min/max, required, pattern, etc.)[AsParameters]AddFluentValidationRules()FluentValidationSchemaTransformerskipped all property-level schemas, but for nested object types this was the only transformer callFull Changelog: micro-elements/MicroElements.Swashbuckle.FluentValidation@v7.1.3...v7.1.4-beta
7.1.3
Changes in 7.1.3
$refreplaced with inline schema copy when usingSetValidatorwith nested object types (Issue #198)ResolveRefProperty(introduced in 7.1.2 for BigInteger isolation) replaced all$refproperties with copies, destroying reference structure in the OpenAPI document$refproperties before rule application, restore them afterwards if no validation constraints were added by rulesFull Changelog: micro-elements/MicroElements.Swashbuckle.FluentValidation@v7.1.2...v7.1.3
Commits viewable in compare view.
Updated Swashbuckle.AspNetCore from 10.1.2 to 10.2.1.
Release notes
Sourced from Swashbuckle.AspNetCore's releases.
10.2.1
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.0...v10.2.1
10.2.0
What's Changed
MapSwaggerUIandMapReDocto support endpoint routing by @Strepto in Add MapSwaggerUI and MapReDoc to support endpoint routing domaindrivendev/Swashbuckle.AspNetCore#3822HEADrequests by @snebjorn in Support HEAD requests domaindrivendev/Swashbuckle.AspNetCore#3887IAsyncSwaggerProviderin CLItofilecommand by @bt-Knodel in Use IAsyncSwaggerProvider in CLI tofile command domaindrivendev/Swashbuckle.AspNetCore#3910New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.7...v10.2.0
10.1.7
What's Changed
New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.6...v10.1.7
10.1.6
What's Changed
New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.5...v10.1.6
10.1.5
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.4...v10.1.5
10.1.4
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.3...v10.1.4
10.1.3
What's Changed
"null"by @jgarciadelanoceda in Fix null examples being represented as the string null domaindrivendev/Swashbuckle.AspNetCore#3788Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.2...v10.1.3
Commits viewable in compare view.
Updated swashbuckle.aspnetcore.cli from 10.1.2 to 10.2.1.
Release notes
Sourced from swashbuckle.aspnetcore.cli's releases.
10.2.1
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.0...v10.2.1
10.2.0
What's Changed
MapSwaggerUIandMapReDocto support endpoint routing by @Strepto in Add MapSwaggerUI and MapReDoc to support endpoint routing domaindrivendev/Swashbuckle.AspNetCore#3822HEADrequests by @snebjorn in Support HEAD requests domaindrivendev/Swashbuckle.AspNetCore#3887IAsyncSwaggerProviderin CLItofilecommand by @bt-Knodel in Use IAsyncSwaggerProvider in CLI tofile command domaindrivendev/Swashbuckle.AspNetCore#3910New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.7...v10.2.0
10.1.7
What's Changed
New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.6...v10.1.7
10.1.6
What's Changed
New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.5...v10.1.6
10.1.5
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.4...v10.1.5
10.1.4
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.3...v10.1.4
10.1.3
What's Changed
"null"by @jgarciadelanoceda in Fix null examples being represented as the string null domaindrivendev/Swashbuckle.AspNetCore#3788Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.2...v10.1.3
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions