We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://github.com/cuelang/cue/blob/master/doc/ref/spec.md#source-code-representation
UTF-8 seems to be the only valid encoding. We could:
The text was updated successfully, but these errors were encountered:
The scanner seems to be quite forgiving:
https://github.com/cuelang/cue/blob/d9d048725a6d2e69c16533ddf87be7368f199740/cue/scanner/scanner.go#L81
Even clearly invalid Unicode is parsed and survives the round-trip through cue eval:
cue eval
echo -ne 'foo: "\xf0\x28\x8c\x28\x7F\xfe\xff"' >> imports.cue
Not sure if this is a bug or a feature.
Sorry, something went wrong.
I have had issues where UTF-16 json files on windows fail to read.
No branches or pull requests
https://github.com/cuelang/cue/blob/master/doc/ref/spec.md#source-code-representation
UTF-8 seems to be the only valid encoding. We could:
The text was updated successfully, but these errors were encountered: