Skip to content

Commit 4cbf2dd

Browse files
committed
small edits
1 parent d1c17ac commit 4cbf2dd

File tree

5 files changed

+5
-4
lines changed

5 files changed

+5
-4
lines changed

.jekyll-metadata

1.85 KB
Binary file not shown.

_docs/schema/basics.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -449,7 +449,7 @@ New formats must be registered via the `Formats.Register()` static method. This
449449
> For the best performance, use a cached evaluation options object.
450450
>
451451
> *JsonSchema.Net* optimizes repeated evaluations with the same schema by performing some static analysis during the first evaluation. However because changes to evaluation options can affect this analysis, the analysis is recalculated if the options change or a new options object is detected.
452-
{: .prompt-warn }
452+
{: .prompt-warning }
453453

454454
The `EvaluationOptions` class gives you a few configuration points for customizing how the evaluation process behaves. It is an instance class and can be passed into the `JsonSchema.Evaluate()` method. If no options are explicitly passed, a copy of `JsonSchemaOptions.Default` will be used.
455455

@@ -469,6 +469,7 @@ _\* If you're using a custom meta-schema, you'll need to load it per the [Schema
469469
Several in the JSON Schema community have raised issues that collecting annotations can be costly in both memory consumption and time. As such, one proposal has been to allow for filtering which annotation are collected and reported in the output.
470470

471471
> Some annotations, like those for `properties`, are still collected but not reported as they are required for other keywords, like `unevaluatedProperties`, to operate.
472+
{: .prompt-info }
472473

473474
By default, all annotations are collected.
474475

_docs/schema/codegen/mini-meta-schemas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ order: "01.6.3"
99
>
1010
> *JsonSchema.Net.CodeGeneration* is no longer being developed.
1111
>
12-
> Please see https://blog.json-everything.net/posts/dropping-codegen/ for more information.
12+
> Please see [https://blog.json-everything.net/posts/dropping-codegen/](https://blog.json-everything.net/posts/dropping-codegen/) for more information.
1313
{: .prompt-danger }
1414

1515
This page serves as a reference to the mini-meta-schemas that are used to identify the supported patterns.

_docs/schema/codegen/patterns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ order: "01.6.2"
99
>
1010
> *JsonSchema.Net.CodeGeneration* is no longer being developed.
1111
>
12-
> Please see https://blog.json-everything.net/posts/dropping-codegen/ for more information.
12+
> Please see [https://blog.json-everything.net/posts/dropping-codegen/](https://blog.json-everything.net/posts/dropping-codegen/) for more information.
1313
{: .prompt-danger }
1414

1515
This page gives more technical information on the various schema patterns that are supported by the code generation functionality.

_docs/schema/codegen/schema-codegen.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ order: "01.6.1"
1010
>
1111
> *JsonSchema.Net.CodeGeneration* is no longer being developed.
1212
>
13-
> Please see https://blog.json-everything.net/posts/dropping-codegen/ for more information.
13+
> Please see [https://blog.json-everything.net/posts/dropping-codegen/](https://blog.json-everything.net/posts/dropping-codegen/) for more information.
1414
{: .prompt-danger }
1515

1616
*JsonSchema.Net.CodeGeneration* is a tool that can create C# code from JSON Schemas.

0 commit comments

Comments
 (0)