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
I think that if explicit_start is set to false, yamlfix should keep existing separators to avoid breaking valid files.
If possible, I think it would be even better if there was a way (explicit_start or otherwise) to tell yamlfix to not mess with the explicit start altogether: Keep it if exists, do not add it if it doesn't, do nothing with other (non-start) separators.
Description
When
explicit_start
is set tofalse
, yamlfix strips all document separators from a file, potentially breaking it.Steps to reproduce
Consider the following file with two documents (
test.yaml
):Running yamlfix with
explicit_start
set tofalse
will break this file:This does not happen if
explicit_start
is true (default):I think that if
explicit_start
is set to false, yamlfix should keep existing separators to avoid breaking valid files.If possible, I think it would be even better if there was a way (
explicit_start
or otherwise) to tell yamlfix to not mess with the explicit start altogether: Keep it if exists, do not add it if it doesn't, do nothing with other (non-start) separators.Environment
The text was updated successfully, but these errors were encountered: