GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — Bump NJsonSchema from 10.5.2 to 10.6.9 by dependabot[bot] · Pull Request #16888 · PowerShell/PowerShell

Conversation

dependabot Bot commented on behalf of github Feb 16, 2022

Copy link

Copy Markdown

Contributor

Bumps NJsonSchema from 10.5.2 to 10.6.9.

Release notes

Sourced from NJsonSchema's releases.

NJsonSchema v10.6.9

Use full namespace for JsonConverterAttribute, RicoSuter/NSwag#3871

NJsonSchema v10.6.8

Fixed C# inheritance code generation for System.Text.Json

Other fixes

NJsonSchema v10.6.7

No release notes provided.

NJsonSchema v10.6.6

Fix bug in Namotion.Reflection

NJsonSchema v10.6.5

AdditionalProperties are only added on the base class (#1451)

Fix ConvertCSharpDocs multi-line regression (#1463)

NJsonSchema v10.6.4

Fixed toolchain version output in code generators

NJsonSchema v10.6.3

More performance improvements

Added UseXmlDocumentation and ResolveExternalXmlDocumentation settings in NJsonSchema

Breaking change: Use these settings instead of XmlDocsExtensions.ResolveFromNuGetCacheOrDotNetSdk

NJsonSchema v10.6.2

Some performance improvements

NJsonSchema v10.6.1

No release notes provided.

NJsonSchema v10.6.0

Breaking change: Migrate from DotLiquid to Fluid (reasons: much faster code generation & more strict liquid implementation)

You need to migrate custom templates: Replace elseif with elsif, fix newline handling (have a look at the updates templates in the repository).

Minor bug fixes

Commits

eb20a66 Use full namespace for JsonConverterAttribute, https://github.com/RicoSuter/N...
e2a60bc Fix STJ inheritance, closes RicoSuter/NSwag#3871
932884e Fix DateFormatConverter for System.Text.Json (#1490)
022ba27 Update Namotion.Reflection
acb54ca Support duration as of JSON Schema 2019-09 (#1478)
ecee450 Lazily allocate list for GetActualSchema (#1483)
057e984 Remove dictionary allocation from TypeResolverBase.Types (#1484)
4ba9982 Give better message from elseif usage (#1479)
69a7739 Remove unnecessary caching in JsonSchemaGeneratorSettings.ResolveContract (#1...
81f6f4c Fix collection empty bug. (#1477)
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)

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions


          Bump NJsonSchema from 10.5.2 to 10.6.9

503251a

Bumps [NJsonSchema](https://github.com/RicoSuter/NJsonSchema) from 10.5.2 to 10.6.9.
- [Release notes](https://github.com/RicoSuter/NJsonSchema/releases)
- [Commits](RicoSuter/NJsonSchema@v10.5.2...v10.6.9)

---
updated-dependencies:
- dependency-name: NJsonSchema
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

dependabot Bot requested review from Paul Higinbotham (PaulHigin), Travis Plunk (TravisEz13), Aditya Patwardhan (adityapatwardhan), Andrew (anmenaga) and Dongbo Wang (daxian-dbw) as code owners

February 16, 2022 18:16

dependabot Bot added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label

Feb 16, 2022

ghost assigned Ilya (iSazonov)

Feb 16, 2022

pull-request-quantifier-deprecated Bot added the Extra Small label

Feb 16, 2022

dependabot Bot mentioned this pull request

Feb 16, 2022

Bump NJsonSchema from 10.5.2 to 10.6.2 #16574

Closed

dependabot Bot assigned Aditya Patwardhan (adityapatwardhan)

Feb 16, 2022


          Update cgmanifest.json

506c919

pull-request-quantifier-deprecated Bot commented Feb 16, 2022

Copy link

Copy Markdown

This PR has 6 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       : +3 -3
Percentile : 2.4%

Total files changed: 2

Change summary by file extension:
.csproj : +1 -1
.json : +2 -2

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 detetcted.
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.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Travis Plunk (TravisEz13) enabled auto-merge (squash)

February 16, 2022 18:25

Travis Plunk (TravisEz13) approved these changes

Feb 16, 2022

View reviewed changes

Travis Plunk (TravisEz13) merged commit fbae40d into master

Feb 16, 2022

Travis Plunk (TravisEz13) deleted the dependabot/nuget/NJsonSchema-10.6.9 branch

February 16, 2022 19:01

Deleted user (ghost) commented Feb 24, 2022

Copy link

Copy Markdown

🎉v7.3.0-preview.2 has been released which incorporates this pull request.:tada:

Handy links:

Release Notes

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj-contribs/PowerShell that referenced this pull request

Aug 6, 2026


          Bump NJsonSchema from 10.5.2 to 10.6.9 (PowerShell#16888)

a9fc440

* Bump NJsonSchema from 10.5.2 to 10.6.9

Bumps [NJsonSchema](https://github.com/RicoSuter/NJsonSchema) from 10.5.2 to 10.6.9.
- [Release notes](https://github.com/RicoSuter/NJsonSchema/releases)
- [Commits](RicoSuter/NJsonSchema@v10.5.2...v10.6.9)

---
updated-dependencies:
- dependency-name: NJsonSchema
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

* Update cgmanifest.json

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Travis Plunk <[email protected]>

Reviewers

Travis Plunk (TravisEz13)

TravisEz13 approved these changes

Dongbo Wang (daxian-dbw)

Awaiting requested review from daxian-dbw

Aditya Patwardhan (adityapatwardhan)

Awaiting requested review from adityapatwardhan

Andrew (anmenaga)

Awaiting requested review from anmenaga

Paul Higinbotham (PaulHigin)

Awaiting requested review from PaulHigin

Uh oh!

There was an error while loading. Please reload this page.

Assignees

Aditya Patwardhan (adityapatwardhan)

Ilya (iSazonov)

Labels

CL-BuildPackaging

Indicates that a PR should be marked as a build or packaging change in the Change Log

Extra Small

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

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.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.