Skip to content

Explicitly specify handling of invalid UTF-8 in CBOR text strings and Cadence strings #49

@fxamacker

Description

@fxamacker

The specification should be explicit about invalid UTF-8 strings.

My preference is to reject invalid UTF-8 text strings. However, there may be edge cases I'm not aware of, so confirm with Cadence team first before adding text.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions