-
Notifications
You must be signed in to change notification settings - Fork 58
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
Remove experimental support for multi-format Netlify config #975
Comments
cc/ @verythorough |
Thanks for the mention! The gradual plan makes sense to me. I'll file associated docs issues as needed (and link them here). |
First step done: replacing test fixtures (#1146). Since I had issues finding a TOML serializer that works, I actually had to do a bunch of |
The next step is: add deprecation warnings and convert users The only thing left after this is in production is (in the future) removing deprecation warnings, conversion and YAML/JSON parsing, making it a breaking change. |
Done. |
Netlify configuration file support for YAML and JSON syntax was introduced as a work-in-progress feature. This issue is being opened in response to the following:
This issue is not about whether we should support this, but about requiring that we support it well if and when we have resources to do so.
Plan for removing support
Future support
To support multiple configuration file formats, this should be re-introduced as a standalone feature with product and engineering input during a discovery phase, and prioritized for proper implementation.
The text was updated successfully, but these errors were encountered: