-
-
Notifications
You must be signed in to change notification settings - Fork 647
Replace go-yaml/yaml with goccy/go-yaml #2298
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
Comments
Totally agree, I actually started doing this late 2023 but hit some snags on their repo. I can see That this was closed recently..worth trying again when I get free time |
@mikefarah Thanks for your effort! Really appreciate your effort! |
@mikefarah Please let me know if the migration is being hindered by an issue with my library. I will prioritize addressing it. |
Hey @mikefarah, will you have time for this soon? And if not, can you offer some general guidance in case I or anyone else finds the time to work on this? |
@mikefarah https://github.com/go-yaml/yaml has been deprecated and archived. Can we please update to using https://github.com/goccy/go-yaml |
Please describe your feature request.
yq
increasingly suffers from the fact that the underlyinggo-yaml/yaml
library is rather unmaintained and lacks some important functionality for someyq
use cases.Describe the solution you'd like
yq
could migrate to a new kid in town, the goccy/go-yaml.According to its README, the library aims to replace the
go-yaml/yaml
library and has some really nice additional features, such as:This feature is in particular interesting for
yq -i
use cases, which unfortunately might modify whitespace due to limitations in thego-yaml/yaml
library.The text was updated successfully, but these errors were encountered: