Skip to content
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 to yaml.v3 #6

Closed
wants to merge 2 commits into from
Closed

migrate to yaml.v3 #6

wants to merge 2 commits into from

Conversation

6543
Copy link

@6543 6543 commented Jan 13, 2022

this is a breaking change and we should think of a major version bump ...

return node.Value
}

return fmt.Sprintf("<do not support yaml node kind '%v'>", node.Kind)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to change api fo this func so we can pass error obj upstream ... - just not done because like to get some ACK to change api of this lib more drastically

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yuin can you ACK Y/N/need-more-discussion?

meta_test.go Show resolved Hide resolved
@6543 6543 changed the title migrateo to yaml.v3 migrate to yaml.v3 Jan 13, 2022
@6543
Copy link
Author

6543 commented Jan 13, 2022

ps: with this we could do more things like solve #4 cc @13rac1

-> go-gitea/gitea#12703
-> go-gitea/gitea#18239

@yuin
Copy link
Owner

yuin commented Feb 8, 2022

Sorry for late reply. This PR seems containing API breaking changes. So it should be v2.

@6543
Copy link
Author

6543 commented Feb 8, 2022

@yuin yes thats why I'm asking if i should propose changes as a whole for a v2

Do you have some channel to chat about it?

@yuin
Copy link
Owner

yuin commented Feb 12, 2022

Sorry, I'm VERY poor at English. I can not chat in English.

And I have less motivation about version up of go-yaml. We do not use complicate functions about YAML. And goldmark users that use this extension most unlikely to write complex YAML in a metadata section. What is your motivation about version up?

@yuin yuin closed this Apr 30, 2022
@6543
Copy link
Author

6543 commented Apr 30, 2022

well is probably the best for now - if you plan a new version for goldmark-meta please reopen this and ping me :) @yuin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants