You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@avro.apache.org by mg...@apache.org on 2024/08/22 06:52:17 UTC
(avro) 03/03: Fix page references in docs
This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch docs-build-fixes
in repository https://gitbox.apache.org/repos/asf/avro.git
commit 2d44f06c4bf84656581b305a7a257009e7456be2
Author: Martin Tzvetanov Grigorov <mg...@apache.org>
AuthorDate: Thu Aug 22 09:51:23 2024 +0300
Fix page references in docs
Fixes the following errors:
```
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:225:37": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:226:31": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:227:41": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:228:51": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:229:63": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:230:31": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/++version++/IDL Language/_index.md:264:212": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:225:37": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:226:31": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:227:41": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:228:51": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:229:63": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:230:31": page reference "specification" is ambiguous
ERROR [en] REF_NOT_FOUND: Ref "specification": "/home/runner/work/avro/avro/doc/content/en/docs/1.12.0/IDL Language/_index.md:264:212": page reference "specification" is ambiguous
```
Signed-off-by: Martin Tzvetanov Grigorov <mg...@apache.org>
---
doc/content/en/docs/++version++/IDL Language/_index.md | 14 +++++++-------
doc/content/en/docs/1.12.0/IDL Language/_index.md | 14 +++++++-------
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/doc/content/en/docs/++version++/IDL Language/_index.md b/doc/content/en/docs/++version++/IDL Language/_index.md
index 7d0121274..68c5605b7 100644
--- a/doc/content/en/docs/++version++/IDL Language/_index.md
+++ b/doc/content/en/docs/++version++/IDL Language/_index.md
@@ -222,12 +222,12 @@ The primitive types supported by Avro IDL are the same as those supported by Avr
### Logical Types
Some of the logical types supported by Avro's JSON format are directly supported by Avro IDL. The currently supported types are:
-* _decimal_ (logical type [decimal]({{< relref "specification#decimal" >}}))
-* _date_ (logical type [date]({{< relref "specification#date" >}}))
-* _time_ms_ (logical type [time-millis]({{< relref "specification#time-millisecond-precision" >}}))
-* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "specification#timestamp-millisecond-precision" >}}))
-* _local_timestamp_ms_ (logical type [local-timestamp-millis]({{< relref "specification#local_timestamp_ms" >}}))
-* _uuid_ (logical type [uuid]({{< relref "specification#uuid" >}}))
+* _decimal_ (logical type [decimal]({{< relref "../specification#decimal" >}}))
+* _date_ (logical type [date]({{< relref "../specification#date" >}}))
+* _time_ms_ (logical type [time-millis]({{< relref "../specification#time-millisecond-precision" >}}))
+* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "../specification#timestamp-millisecond-precision" >}}))
+* _local_timestamp_ms_ (logical type [local-timestamp-millis]({{< relref "../specification#local_timestamp_ms" >}}))
+* _uuid_ (logical type [uuid]({{< relref "../specification#uuid" >}}))
For example:
```java
@@ -261,7 +261,7 @@ record Card {
```
### Default Values
-Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "specification#schema-record" >}}).
+Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "../specification#schema-record" >}}).
### Complex Types
diff --git a/doc/content/en/docs/1.12.0/IDL Language/_index.md b/doc/content/en/docs/1.12.0/IDL Language/_index.md
index 7d0121274..68c5605b7 100644
--- a/doc/content/en/docs/1.12.0/IDL Language/_index.md
+++ b/doc/content/en/docs/1.12.0/IDL Language/_index.md
@@ -222,12 +222,12 @@ The primitive types supported by Avro IDL are the same as those supported by Avr
### Logical Types
Some of the logical types supported by Avro's JSON format are directly supported by Avro IDL. The currently supported types are:
-* _decimal_ (logical type [decimal]({{< relref "specification#decimal" >}}))
-* _date_ (logical type [date]({{< relref "specification#date" >}}))
-* _time_ms_ (logical type [time-millis]({{< relref "specification#time-millisecond-precision" >}}))
-* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "specification#timestamp-millisecond-precision" >}}))
-* _local_timestamp_ms_ (logical type [local-timestamp-millis]({{< relref "specification#local_timestamp_ms" >}}))
-* _uuid_ (logical type [uuid]({{< relref "specification#uuid" >}}))
+* _decimal_ (logical type [decimal]({{< relref "../specification#decimal" >}}))
+* _date_ (logical type [date]({{< relref "../specification#date" >}}))
+* _time_ms_ (logical type [time-millis]({{< relref "../specification#time-millisecond-precision" >}}))
+* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "../specification#timestamp-millisecond-precision" >}}))
+* _local_timestamp_ms_ (logical type [local-timestamp-millis]({{< relref "../specification#local_timestamp_ms" >}}))
+* _uuid_ (logical type [uuid]({{< relref "../specification#uuid" >}}))
For example:
```java
@@ -261,7 +261,7 @@ record Card {
```
### Default Values
-Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "specification#schema-record" >}}).
+Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "../specification#schema-record" >}}).
### Complex Types