Skip to content

[2021-06-03] Ensure clarity in the unicode support spec changes #778

@benjie

Description

@benjie

Ivan: I mean like a String value - if I send surrogate pair inside as a literal; that'll be transcoded into proper code. What if I send it via variables, what happens to the surrogate pairs there? Potentially people can inline arguments (e.g. simplification of queries), so we need feature parity with query variables.
Lee: I agree we should generally have the same. The Unicode rules we apply to the grammar do not apply to values that come in in the same way (because the Spec doesn't have purview over them). This spec change hopefully clarifies some of this. As long as your internal string can represent the value then you're good to go. We'll take a careful look at the text to make sure that we repeat this point wherever needed, e.g. in the serialization section.


Note: Action Item issues are reviewed and closed during Working Group
meetings.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions