Skip to content
New issue

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

Define acceptable file formats for file configuration #3466

Closed
jack-berg opened this issue May 2, 2023 · 1 comment · Fixed by #4017
Closed

Define acceptable file formats for file configuration #3466

jack-berg opened this issue May 2, 2023 · 1 comment · Fixed by #4017
Assignees
Labels
area:configuration Related to configuring the SDK spec:miscellaneous For issues that don't match any other spec label

Comments

@jack-berg
Copy link
Member

Complete outstanding TODO to define acceptable file format.

The OTEP called for JSON or YAML to be supported, with a preference for YAML.

@jack-berg jack-berg added the spec:miscellaneous For issues that don't match any other spec label label May 2, 2023
@jack-berg
Copy link
Member Author

YAML file format was defined in #3744. There's an open TODO for defining JSON format.

I'm personally in favor of only supporting YAML, removing the JSON TODO and closing this issue. Introducing JSON would come likely come with language stating that implementations should support one of JSON or YAML, but need not support both. This would be a bad user experience since we'd loose the ability to have configuration files portable across languages. Not good. Better to support only YAML, even if it means adds a dependency on a YAML parser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:configuration Related to configuring the SDK spec:miscellaneous For issues that don't match any other spec label
Development

Successfully merging a pull request may close this issue.

2 participants