You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We only need to worry about explicitly supporting UTF-8 where we manually process strings. Otherwise encoding is handled by the source or destination of strings (e.g. the shell for the CLI, and files for param codecs).
Both JSON and YAML support UTF-8, and the parsing libraries we use take UTF-8 as the default encoding.
Areas for concern:
param/param_helpers
The text was updated successfully, but these errors were encountered:
We only need to worry about explicitly supporting UTF-8 where we manually process strings. Otherwise encoding is handled by the source or destination of strings (e.g. the shell for the CLI, and files for param codecs).
Both JSON and YAML support UTF-8, and the parsing libraries we use take UTF-8 as the default encoding.
Areas for concern:
param/param_helpers
The text was updated successfully, but these errors were encountered: