Skip to content

Commit 58f67f7

Browse files
committed
int64 instead of double for numeric string example
The format registry currently doesn't specify that double works with strings, so pick something that works with strings as of now.
1 parent 072c562 commit 58f67f7

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/oas.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1918,13 +1918,13 @@ content:
19181918
const: addString
19191919
- properties:
19201920
event:
1921-
const: addNumber
1921+
const: addInt64
19221922
data:
19231923
$comment: |
19241924
Since the data field is a string,
1925-
we need a format to signal that
1926-
it should be handled as a number
1927-
format: double
1925+
we need a format to signal that it
1926+
should be handled as a 64-bit integer.
1927+
format: int64
19281928
- properties:
19291929
event:
19301930
const: addJson
@@ -1953,7 +1953,7 @@ data: This data is formatted
19531953
data: across two lines
19541954
retry: 5
19551955
1956-
event: addNumber
1956+
event: addInt64
19571957
data: 1234.5678
19581958
unknownField: this is ignored
19591959
@@ -1966,7 +1966,7 @@ To more clearly see how this stream is handled, the following is the equivalent
19661966

19671967
```JSONL
19681968
{"event": "addString", "data": "This data is formatted\nacross two lines", "retry": 5}
1969-
{"event": "addNumber", "data": "1234.5678"}
1969+
{"event": "addInt64", "data": "1234.5678"}
19701970
{"event": "addJSON", "data": "{\"foo\": 42}"}
19711971
```
19721972

0 commit comments

Comments
 (0)