Skip to content

Commit cf8c6df

Browse files
authored
Merge pull request #137 from jmespath-community/feature/jep12-doc
Documented JEP-12 legacy syntax deprecation.
2 parents 04989ab + 743d09d commit cf8c6df

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

GRAMMAR.ABNF

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -650,6 +650,16 @@ literal = "`" json-text "`" ;; # Literal Expressions
650650
;; literal values. Note that the \` character must now be escaped in a json-value which means implementations need to
651651
;; handle this case before passing the resulting string to a JSON parser.
652652
;;
653+
;; ```note
654+
;; When [JEP-12](https://github.com/jmespath-community/jmespath.spec/blob/main/jep-012-raw-string-literals.md)
655+
;; introduced raw string literals, a legacy behavior in which backtick literals
656+
;; containing invalid JSON text would be interpreted as if their contents were wrapped
657+
;; in double quotes (e.g., `` `foo` == `"foo"` ``) was deprecated but implementations
658+
;; were allowed to continue supporting it.
659+
;;
660+
;; In this version of the specification, that behavior has been fully removed.
661+
;; ```
662+
;;
653663
;; ## Examples
654664
;; ```
655665
;; search(`"foo"`, "anything") -> "foo"

0 commit comments

Comments
 (0)