Skip to content

Commit d4e9daa

Browse files
authored
fix: lint (#1764)
1 parent b643abf commit d4e9daa

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

source/extended-json/extended-json.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -676,7 +676,9 @@ query operator use case will require that the rules set forth in the 1.0.0 versi
676676
for `$regex`; specifically, that a document with a `$regex` key whose value is a JSON object should be parsed as a
677677
normal document and not reported as an error.
678678

679-
**Q**. How can implementations which require backwards compatibility with Legacy Extended JSON, in which BSON binary values were represented like `{"$binary": "AQIDBAU=", "$type": "80"}`, handle parsing of extended JSON test representing a MongoDB query filter containing the `$type`operator?
679+
**Q**. How can implementations which require backwards compatibility with Legacy Extended JSON, in which BSON binary
680+
values were represented like `{"$binary": "AQIDBAU=", "$type": "80"}`, handle parsing of extended JSON test representing
681+
a MongoDB query filter containing the `$type`operator?
680682

681683
**A**. An implementation can handle this in a number of ways:
682684

0 commit comments

Comments
 (0)