This is an automated email from the ASF dual-hosted git repository.
fokko pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/avro.git
The following commit(s) were added to refs/heads/main by this push:
new 4d4e75528 Fix relative links
4d4e75528 is described below
commit 4d4e75528977cad715286b8c3acc10c5148001e7
Author: Fokko <[email protected]>
AuthorDate: Sun Aug 25 22:02:57 2024 +0200
Fix relative links
---
doc/content/en/docs/1.11.1/IDL Language/_index.md | 10 +++++-----
doc/content/en/docs/1.11.2/IDL Language/_index.md | 12 ++++++------
doc/content/en/docs/1.11.3/IDL Language/_index.md | 12 ++++++------
3 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/doc/content/en/docs/1.11.1/IDL Language/_index.md
b/doc/content/en/docs/1.11.1/IDL Language/_index.md
index 6ca0deb7b..c14053937 100644
--- a/doc/content/en/docs/1.11.1/IDL Language/_index.md
+++ b/doc/content/en/docs/1.11.1/IDL Language/_index.md
@@ -170,10 +170,10 @@ 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 also 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" >}}))
+* _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" >}}))
For example:
```java
@@ -206,7 +206,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.11.2/IDL Language/_index.md
b/doc/content/en/docs/1.11.2/IDL Language/_index.md
index 8fe3d0592..f50b0a489 100644
--- a/doc/content/en/docs/1.11.2/IDL Language/_index.md
+++ b/doc/content/en/docs/1.11.2/IDL Language/_index.md
@@ -170,11 +170,11 @@ 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 also 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" >}}))
-* _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" >}}))
+* _uuid_ (logical type [uuid]({{< relref "../specification#uuid" >}}))
For example:
```java
@@ -208,7 +208,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.11.3/IDL Language/_index.md
b/doc/content/en/docs/1.11.3/IDL Language/_index.md
index 8fe3d0592..f50b0a489 100644
--- a/doc/content/en/docs/1.11.3/IDL Language/_index.md
+++ b/doc/content/en/docs/1.11.3/IDL Language/_index.md
@@ -170,11 +170,11 @@ 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 also 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" >}}))
-* _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" >}}))
+* _uuid_ (logical type [uuid]({{< relref "../specification#uuid" >}}))
For example:
```java
@@ -208,7 +208,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
