rebuilt documentation

docs/index.json

@@ -991,8 +991,8 @@
   },
   "release-notes/json-schema.html": {
     "href": "release-notes/json-schema.html",
-    "title": "1.9.1",
-    "keywords": "1.9.1 Fixes found by the release of the 2020-12 test suite. $dynamicAnchor and $dynamicRef behavior. make items and unevaluatedItems respect annotations from prefixItems . 1.9.0 Added support for nullable reference types. Fixed various evaluation bugs around the various keywords involved with references. Fixed content* keywords so that they only validate if the instance is a string. Fixed #76 - .GetHashCode() is inconsistent for schemas and keywords. Credit to @amosonn for pointing me to a good hash code method in the wild. RecursiveRef parameterless constructor marked obsolete in favor of new constructor which takes a boolean value. Schema builder extension also updated to include a parameter which defaults to true to maintain current behavior. 1.8.0 Exposed UriExtensions to help support new keywords that manipulate URIs. 1.7.1 Fixed #67 - enum keyword serializes as examples due to a copy-paste error. Credit to @dannyheard7 for finding and fixing. Also fixed several other related serialization issues. 1.7.0 Updated hard-coded 2020-12 meta-schemas to match the published documents. Added the following JsonSchemaBuilder extension method overloads: .DynamicRef(string) .Const(JsonElementProxy) .Default(JsonElementProxy) .Enum(IEnumerable<JsonElementProxy>) .Enum(params JsonElementProxy[]) .Examples(IEnumerable<JsonElement>) .Examples(IEnumerable<JsonElementProxy>) .Examples(params JsonElementProxy[]) (See Json.More.Net v1.3.0 for more information on JsonElementProxy .) 1.6.1 Signed the DLL for strong name compatibility. 1.6.0 Added support for Draft 2020-12. Meta-schema validation now always occurs superficially in that it validates that the meta-schema is known. The ValidationOptions.ValidateMetaSchema option now only controls whether a full meta-schema validation of the schema will occur. This should only affect clients validating schemas declaring custom meta-schemas with the $schema keyword. Custom meta-schemas will now need to be loaded into the system manually or SchemaRegistry.Fetch will need to be set to retrieve it automatically. Added all new vocabularies and meta-schemas. New keywords: $dynamicRef - replaces/augments $recursiveRef $dynamicAnchor - replaces/augments $recursivAnchor prefixItems - replaces array-form items Added JsonSchemaBuilder extension method for $anchor which should have been added for draft 2019-09 support. ValidationOptions.ValidateFormat has been obsoleted and replaced by ValidationOptions.RequireFormatValidation with the same semantics and default. FormatKeyword now responds to the presence of the format vocabularies in the meta-schema declared by the $schema keyword as well as the ValidationOptions.RequireFormatValidation option. (Includes a bug fix for draft 2019-09 schemas that use a meta-schema that declare the format vocabulary with a value of true .) 1.5.4 Added debug symbols to package. No functional change. 1.5.3 Fixed NullReferenceException when comparing two schemas. 1.5.2 Updated wording for enum error message. This must remain generic and cannot include the expected values because the list could be long and the values could be quite large. 1.5.1 #35 JsonSchema.FromFile() handles file paths as URIs incorrectly in non-Windows systems. 1.5.0 #33 Added ValidationOptions.ValidateFormat which allows configuration of whether to validate the format keyword. Also fixes a bug where the format keyword was validated by default for draft 2019-09 which specifies that it should only generate annotations by default. Because this library favors the latest draft, this is the default behavior for all drafts. As a further followup to #27 (below), basic output has been refined. 1.4.0 #27 (reopened) Better reduction of detailed output format which eliminates the notion that any nodes must be kept. #29 Relative $id keyword at root of schema was not supported. Added ValidationOptions.DefaultBaseUri to be used when no other absolute URI is defined by the $id keyword. Also now supports assuming the base URI from the file name. 1.3.1 #27 Nodes in the basic and detailed output formats that match the overall outcome should be removed. This also addresses several other bugs involving the output such as absoluteKeywordLocation . 1.3.0 #15 Easier navigation of the schema and its subschemas. Added ISchemaContainer , ISchemaCollector , and IKeyedSchemaCollector for the varying sets of subschemas that keywords can have. Added SchemaKeywordExtensions.GetSubschemas() extension method. #19 Keyword filtering doesn't consider declared draft or ValidationOptions.ValidateAs . 1.2.0 ( json-schema .org #358 ) Published draft 06 meta-schema doesn't match the copy in the spec repo. #16 JsonSchema equality checking. Along with this, added IEquatable<T> to SchemaKeywordRegistry.Register<T>() . #18 properties keyword is processed with same priority as additionalProperties making keyword order important, but it shouldn't be. Added EnumerableExtensions.ContentsEqual() . 1.1.0 Added SchemaRegistry.Fetch property to enable automatic downloading of referenced schemas. 1.0.3 #9 if / then / else are processed in serialized order instead of processing if first. #10 Bug fix around deserialization of readonly keyword. 1.0.2 Updated format json-pointer to require plain pointers. URI-encoded pointers are invalid. 1.0.1 Updated validation of formats hostname , iri , uri , regex , and time . Fixed issue resolving references ( $ref & $recursiveRef ) to miscellaneous (non-keyword) schema data. 1.0.0 Initial release."
+    "title": "1.9.2",
+    "keywords": "1.9.2 #79 - $ref was calling out to resolve a parent URI. 1.9.1 Fixes found by the release of the 2020-12 test suite. $dynamicAnchor and $dynamicRef behavior. make items and unevaluatedItems respect annotations from prefixItems . 1.9.0 Added support for nullable reference types. Fixed various evaluation bugs around the various keywords involved with references. Fixed content* keywords so that they only validate if the instance is a string. Fixed #76 - .GetHashCode() is inconsistent for schemas and keywords. Credit to @amosonn for pointing me to a good hash code method in the wild. RecursiveRef parameterless constructor marked obsolete in favor of new constructor which takes a boolean value. Schema builder extension also updated to include a parameter which defaults to true to maintain current behavior. 1.8.0 Exposed UriExtensions to help support new keywords that manipulate URIs. 1.7.1 Fixed #67 - enum keyword serializes as examples due to a copy-paste error. Credit to @dannyheard7 for finding and fixing. Also fixed several other related serialization issues. 1.7.0 Updated hard-coded 2020-12 meta-schemas to match the published documents. Added the following JsonSchemaBuilder extension method overloads: .DynamicRef(string) .Const(JsonElementProxy) .Default(JsonElementProxy) .Enum(IEnumerable<JsonElementProxy>) .Enum(params JsonElementProxy[]) .Examples(IEnumerable<JsonElement>) .Examples(IEnumerable<JsonElementProxy>) .Examples(params JsonElementProxy[]) (See Json.More.Net v1.3.0 for more information on JsonElementProxy .) 1.6.1 Signed the DLL for strong name compatibility. 1.6.0 Added support for Draft 2020-12. Meta-schema validation now always occurs superficially in that it validates that the meta-schema is known. The ValidationOptions.ValidateMetaSchema option now only controls whether a full meta-schema validation of the schema will occur. This should only affect clients validating schemas declaring custom meta-schemas with the $schema keyword. Custom meta-schemas will now need to be loaded into the system manually or SchemaRegistry.Fetch will need to be set to retrieve it automatically. Added all new vocabularies and meta-schemas. New keywords: $dynamicRef - replaces/augments $recursiveRef $dynamicAnchor - replaces/augments $recursivAnchor prefixItems - replaces array-form items Added JsonSchemaBuilder extension method for $anchor which should have been added for draft 2019-09 support. ValidationOptions.ValidateFormat has been obsoleted and replaced by ValidationOptions.RequireFormatValidation with the same semantics and default. FormatKeyword now responds to the presence of the format vocabularies in the meta-schema declared by the $schema keyword as well as the ValidationOptions.RequireFormatValidation option. (Includes a bug fix for draft 2019-09 schemas that use a meta-schema that declare the format vocabulary with a value of true .) 1.5.4 Added debug symbols to package. No functional change. 1.5.3 Fixed NullReferenceException when comparing two schemas. 1.5.2 Updated wording for enum error message. This must remain generic and cannot include the expected values because the list could be long and the values could be quite large. 1.5.1 #35 JsonSchema.FromFile() handles file paths as URIs incorrectly in non-Windows systems. 1.5.0 #33 Added ValidationOptions.ValidateFormat which allows configuration of whether to validate the format keyword. Also fixes a bug where the format keyword was validated by default for draft 2019-09 which specifies that it should only generate annotations by default. Because this library favors the latest draft, this is the default behavior for all drafts. As a further followup to #27 (below), basic output has been refined. 1.4.0 #27 (reopened) Better reduction of detailed output format which eliminates the notion that any nodes must be kept. #29 Relative $id keyword at root of schema was not supported. Added ValidationOptions.DefaultBaseUri to be used when no other absolute URI is defined by the $id keyword. Also now supports assuming the base URI from the file name. 1.3.1 #27 Nodes in the basic and detailed output formats that match the overall outcome should be removed. This also addresses several other bugs involving the output such as absoluteKeywordLocation . 1.3.0 #15 Easier navigation of the schema and its subschemas. Added ISchemaContainer , ISchemaCollector , and IKeyedSchemaCollector for the varying sets of subschemas that keywords can have. Added SchemaKeywordExtensions.GetSubschemas() extension method. #19 Keyword filtering doesn't consider declared draft or ValidationOptions.ValidateAs . 1.2.0 ( json-schema .org #358 ) Published draft 06 meta-schema doesn't match the copy in the spec repo. #16 JsonSchema equality checking. Along with this, added IEquatable<T> to SchemaKeywordRegistry.Register<T>() . #18 properties keyword is processed with same priority as additionalProperties making keyword order important, but it shouldn't be. Added EnumerableExtensions.ContentsEqual() . 1.1.0 Added SchemaRegistry.Fetch property to enable automatic downloading of referenced schemas. 1.0.3 #9 if / then / else are processed in serialized order instead of processing if first. #10 Bug fix around deserialization of readonly keyword. 1.0.2 Updated format json-pointer to require plain pointers. URI-encoded pointers are invalid. 1.0.1 Updated validation of formats hostname , iri , uri , regex , and time . Fixed issue resolving references ( $ref & $recursiveRef ) to miscellaneous (non-keyword) schema data. 1.0.0 Initial release."
   },
   "release-notes/json-schema-data.html": {
     "href": "release-notes/json-schema-data.html",

docs/manifest.json

@@ -2497,7 +2497,7 @@
       "output": {
         ".html": {
           "relative_path": "release-notes/json-schema.html",
-          "hash": "j6cvf+BW1AIWbuvCMmebfg=="
+          "hash": "IrhNT4PoUR2ImAt8CCMv7w=="
         }
       },
       "is_incremental": false,

docs/release-notes/json-schema.html

@@ -5,9 +5,9 @@
   <head>
     <meta charset="utf-8">
     <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
-    <title>1.9.1 </title>
+    <title>1.9.2 </title>
     <meta name="viewport" content="width=device-width">
-    <meta name="title" content="1.9.1 ">
+    <meta name="title" content="1.9.2 ">
     <meta name="generator" content="docfx 2.56.6.0">
 
     <link rel="shortcut icon" href="../favicon.ico">
@@ -77,8 +77,10 @@
         <div class="article row grid-right">
           <div class="col-md-10">
             <article class="content wrap" id="_content" data-uid="">
-<h1 id="191"><a href="https://github.com/gregsdennis/json-everything/pull/77">1.9.1</a></h1>
+<h1 id="192"><a href="https://github.com/gregsdennis/json-everything/pull/80">1.9.2</a></h1>
 
+<p><a href="https://github.com/gregsdennis/json-everything/issues/79">#79</a> - <code>$ref</code> was calling out to resolve a parent URI.</p>
+<h1 id="191"><a href="https://github.com/gregsdennis/json-everything/pull/77">1.9.1</a></h1>
 <p>Fixes found by the release of the 2020-12 test suite.</p>
 <ul>
 <li><code>$dynamicAnchor</code> and <code>$dynamicRef</code> behavior.</li>