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

Enable anyconfig to handle yaml merge syntax properly #88

Merged
merged 1 commit into from
Jun 11, 2018
Merged

Enable anyconfig to handle yaml merge syntax properly #88

merged 1 commit into from
Jun 11, 2018

Conversation

idanov
Copy link
Contributor

@idanov idanov commented Jun 8, 2018

Fix anyconfig's yaml backend to handle yaml merge syntax and address #87

@idanov idanov changed the title Enable anyconfig to handle yaml merge syntax properly #87 Enable anyconfig to handle yaml merge syntax properly Jun 8, 2018
@coveralls
Copy link

coveralls commented Jun 8, 2018

Coverage Status

Coverage increased (+0.005%) to 92.628% when pulling a24d4b3 on idanov:master into c71c0c5 on ssato:master.

@ssato ssato merged commit d8709b2 into ssato:master Jun 11, 2018
@ssato
Copy link
Owner

ssato commented Jun 11, 2018

Thanks a lot! I was not aware of the issue at all. LGTM and merged.

@idanov
Copy link
Contributor Author

idanov commented Jun 11, 2018

Thanks for merging it! I even didn't know about this feature in YAML until we needed it in a project :) Do you plan to release a new version to PyPI soon which will include the change?

@ssato
Copy link
Owner

ssato commented Jun 13, 2018

Do you plan to release a new version to PyPI soon which will include the change?
I'm planning to release it soon if I could stabilize pathlib support and others new functions including this. Please wait for a while.

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.

3 participants