From f2e590a147b6e09d078cefcc8b0e9e66c261bb40 Mon Sep 17 00:00:00 2001 From: Justin Powers Date: Sat, 15 Jan 2022 03:02:23 -0600 Subject: [PATCH] Fix broken named anchor link (#1870) Prefix the closing angle bracket with a forward slash so that a correct stub is generated for table of contents. --- docs/options.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/options.md b/docs/options.md index 557cf36a8..c1a2ef152 100644 --- a/docs/options.md +++ b/docs/options.md @@ -185,17 +185,17 @@ Option values: - `true` (default) - use unicode flag "u". - `false` - do not use flag "u". -### timestamp +### timestamp Defines which Javascript types will be accepted for the [JTD timestamp type](./json-type-definition#type-form). By default Ajv will accept both Date objects and [RFC3339](https://datatracker.ietf.org/doc/rfc3339/) strings. You can specify allowed values with the option `timestamp: "date"` or `timestamp: "string"`. -### parseDate +### parseDate Defines how date-time strings are parsed by [JTD parsers](./api.md#jtd-parse). By default Ajv parses date-time strings as string. Use `parseDate: true` to parse them as Date objects. -### allowDate +### allowDate Defines how date-time strings are parsed and validated. By default Ajv only allows full date-time strings, as required by JTD specification. Use `allowDate: true` to allow date strings both for validation and for parsing. @@ -203,7 +203,7 @@ Defines how date-time strings are parsed and validated. By default Ajv only allo This option makes JTD validation and parsing more permissive and non-standard. The date strings without time part will be accepted by Ajv, but will be rejected by other JTD validators. ::: -### int32range +### int32range Can be used to disable range checking for `int32` and `uint32` types.