nuget-dressca: Bump the nswag-packages group with 2 updates#5381
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
nuget-dressca: Bump the nswag-packages group with 2 updates#5381dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps NSwag.AspNetCore from 14.6.3 to 14.7.1 Bumps NSwag.MSBuild from 14.6.3 to 14.7.1 --- updated-dependencies: - dependency-name: NSwag.AspNetCore dependency-version: 14.7.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nswag-packages - dependency-name: NSwag.MSBuild dependency-version: 14.7.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nswag-packages ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Test Result 📝Test was a success. Coverage 📐Summary
Dressca.ApplicationCore - 93.5%
Dressca.EfInfrastructure - 14.3%
Dressca.Store.Assets.StaticFiles - 17.2%
Dressca.SystemCommon - 42.3%
Dressca.Web - 32.1%
Dressca.Web.Admin - 29.9%
Dressca.Web.Admin.Dto - 0%
|
Test Result 📝Test was a success. Coverage 📐Summary
Dressca.ApplicationCore - 96%
Dressca.EfInfrastructure - 16.6%
Dressca.Store.Assets.StaticFiles - 17.2%
Dressca.SystemCommon - 42.3%
Dressca.Web - 39.9%
Dressca.Web.Consumer - 53.1%
Dressca.Web.Consumer.Dto - 57.4%
|
Contributor
Author
|
Superseded by #5391. |
dependabot
Bot
deleted the
dependabot/nuget/samples/Dressca/dressca-backend/nswag-packages-674688d9de
branch
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 NSwag.AspNetCore from 14.6.3 to 14.7.1.
Release notes
Sourced from NSwag.AspNetCore's releases.
14.7.1
Corrections to v14.7.0
v14.7.1 updates to NJsonSchema v11.6.1, which corrects the handling of the C#
requiredkeyword and[JsonRequired]:string?,T?) is preserved.MinLength=1on non-nullable strings.[Required]semantics remain unchanged (still suppresses nullability and addsMinLength=1to strings by default, matching its runtime behavior).Observable client changes vs v14.7.0
For
public required string[]? OptionList { get; init; }(#5359):optionList: string[]❌public string[] OptionList❌optionList: string[] | null✅public string[]? OptionList✅For full details and truth tables across all
required/[Required]/[JsonRequired]/[JsonProperty(Required=*)]combinations, see the NJsonSchema v11.6.1 release notes and NJsonSchema #1919.What's Changed
Full Changelog: RicoSuter/NSwag@v14.7.0...v14.7.1
14.7.0
What's Changed
NSwag.Npmresulting in aNConsole.UnusedArgumentExceptionby @ptasev in Fix specifying runtime forNSwag.Npmresulting in aNConsole.UnusedArgumentExceptionRicoSuter/NSwag#5320NJsonSchema v11.6.0 (potentially breaking changes)
This release updates to NJsonSchema v11.6.0 and Namotion.Reflection v3.5.0, which include the following changes that may affect generated code:
requiredkeyword now correctly recognized: Properties using the C# 11requiredkeyword (viaRequiredMemberAttribute/JsonRequiredAttribute) are now properly treated as required in the schema and generated code. Previously these were incorrectly treated as optional.WriteAccessorsetting to control property setter syntax (setvsinit).JsonLibraryVersionsetting for controlling enum attribute generation with System.Text.Json.MinLengthvalidation no longer incorrectly applied to DateTime properties.IncludeFieldsis enabled.For the full list of changes, see the NJsonSchema v11.6.0 release notes.
New Contributors
NSwag.Npmresulting in aNConsole.UnusedArgumentExceptionRicoSuter/NSwag#5320Full Changelog: RicoSuter/NSwag@v14.6.3...v14.7.0
Commits viewable in compare view.
Updated NSwag.MSBuild from 14.6.3 to 14.7.1.
Release notes
Sourced from NSwag.MSBuild's releases.
14.7.1
Corrections to v14.7.0
v14.7.1 updates to NJsonSchema v11.6.1, which corrects the handling of the C#
requiredkeyword and[JsonRequired]:string?,T?) is preserved.MinLength=1on non-nullable strings.[Required]semantics remain unchanged (still suppresses nullability and addsMinLength=1to strings by default, matching its runtime behavior).Observable client changes vs v14.7.0
For
public required string[]? OptionList { get; init; }(#5359):optionList: string[]❌public string[] OptionList❌optionList: string[] | null✅public string[]? OptionList✅For full details and truth tables across all
required/[Required]/[JsonRequired]/[JsonProperty(Required=*)]combinations, see the NJsonSchema v11.6.1 release notes and NJsonSchema #1919.What's Changed
Full Changelog: RicoSuter/NSwag@v14.7.0...v14.7.1
14.7.0
What's Changed
NSwag.Npmresulting in aNConsole.UnusedArgumentExceptionby @ptasev in Fix specifying runtime forNSwag.Npmresulting in aNConsole.UnusedArgumentExceptionRicoSuter/NSwag#5320NJsonSchema v11.6.0 (potentially breaking changes)
This release updates to NJsonSchema v11.6.0 and Namotion.Reflection v3.5.0, which include the following changes that may affect generated code:
requiredkeyword now correctly recognized: Properties using the C# 11requiredkeyword (viaRequiredMemberAttribute/JsonRequiredAttribute) are now properly treated as required in the schema and generated code. Previously these were incorrectly treated as optional.WriteAccessorsetting to control property setter syntax (setvsinit).JsonLibraryVersionsetting for controlling enum attribute generation with System.Text.Json.MinLengthvalidation no longer incorrectly applied to DateTime properties.IncludeFieldsis enabled.For the full list of changes, see the NJsonSchema v11.6.0 release notes.
New Contributors
NSwag.Npmresulting in aNConsole.UnusedArgumentExceptionRicoSuter/NSwag#5320Full Changelog: RicoSuter/NSwag@v14.6.3...v14.7.0
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