Skip to content
This repository was archived by the owner on Nov 7, 2024. It is now read-only.

Conversation

@eternal-flame-AD
Copy link
Member

Added test to make sure the functionality is right.

Signed-off-by: eternal-flame-AD yume@yumechi.jp

Signed-off-by: eternal-flame-AD <yume@yumechi.jp>
@@ -1,31 +1,32 @@
package configor
Copy link
Member

Choose a reason for hiding this comment

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

Have you considered using upstream https://github.com/jinzhu/configor which is already upgraded to yaml v3?

(I'm okay with merging and not using upstream, just a question)

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm thinking about that as well, I was just looking at this diff and can't figure out what exactly the difference in behavior this cause, the code seems to do more than the commit message says.

84c96aa

I added the test to upstream it passed so I think it should suffice for our case.

Copy link
Member

Choose a reason for hiding this comment

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

Not sure anymore why I used this fork. I think it was mostly because of some println stuff. Using jinzhu/configor directly seems to work fine with gotify/server, maybe we use upstream directly instead of the fork?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants