-
Notifications
You must be signed in to change notification settings - Fork 12
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
Migrate from serde_yaml to serde_yml #80
Comments
Thank you for raising the issue! After serde_yaml was archived, no official replacement was specified. I am positive about the migration, but would like to know if there is any information that would help me decide on |
I guess it is up to you to evaluate serde_yml and its goals going forward, considering it was forked from the original.
Maybe consider reaching out to the new maintainer(s) and establish a joint path forward. Using another yaml serde project in your own library could potentially mean breaking changes. I have created a PR with required changes to migrate as you most likely have seen already. |
PR is also confirmed. Thanks for your contribution!!
I'm not used to this kind of communication without GitHub. |
You can reach him via his github handle, he has multiple social network contacts you can try. |
What I meant to say is that I know you created PR, but I have not made the decision that we should move to If I decide to move to |
As
serde_yaml
has been archived and is marked as deprecated it would be good to move toserde_yml
, as it seems to be the successor.The text was updated successfully, but these errors were encountered: