-
Notifications
You must be signed in to change notification settings - Fork 3
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
Implement and test alternative yaml library (goccy/yaml) #9
Implement and test alternative yaml library (goccy/yaml) #9
Comments
This issue has been automatically marked as stale due to no recent activity for the last 60 days. |
Today we use: buildkite/yaml (last commit Oct 16th, 2018) Above is a fork of: go-yaml/yaml (last commit Jun 2nd, 2020) The option we are thinking about moving toward: goccy/yaml (last commit Sep 18th, 2020) |
Initial PR testing out the goccy/go-yaml library Types ad-hoc tests looked good but the real testing will need to happen once this change is pulled into the compiler. |
go-vela/types#118 was reverted in go-vela/types#144 I don't see a description of why they were reverted or where exactly behavior differs between buildkite/yaml and goccy/go-yaml. Was it merge keys or anchors or ...? |
Description
Original stories:
Update our gopkg.in/yaml library to the v3 functionality.
https://github.com/go-yaml/yaml/tree/v3
Value
Definition of Done
This repo is using the
v3
release of thegopkg.in/yaml
library.Effort (Optional)
1 week
Impacted Personas (Optional)
everyone
The text was updated successfully, but these errors were encountered: