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
Allow parsing empty files without throwing error #340
Comments
Sounds like a good idea. |
Awesome I'll post up a PR (on my personal account, this is my work account) |
Looks like I can't post PRs here, but I think I got most of the way there - got a bit stuck with the generics, but would love your opinion on how to close this out. I added the following:
Won't compile to a generics issue, but I think it's pretty close. Thoughts? |
What's the error ? |
I am ready to release 2.6.0 |
I'd love to get this added so I can begin using it right away (all my config files have "THIS FILE CANNOT BE LEFT BLANK" right now for the ones that aren't yet filled in, which is not ideal!) The error my change is giving me is:
My change is returning Validated<ConfigFailure.MultipleFailures, Any> vs. the expected Validated<ConfigFailure, Node>, and I can't quite figure out how to make it happy. Since it doesn't seem like I'm able to push up PRs, it's probably best if you do it (but I'm keen on seeing how you do it after digging into the code in detail yesterday!) |
if you copy paste those two changes into the files as described, you should be able to reproduce easily - (or you can give me perms to push up a PR) |
On github the way you do PRs for public projects is you fork the repo, push to your fork, and PR from fork to repo. |
oh - thanks for the tip - I'll try that out |
This now works in 2.6.0 ConfigLoaderBuilder.default().allowEmptySources.... |
I'd like to be able to pass in empty files and not have the yml parser throw, such as:
What do you think?
The text was updated successfully, but these errors were encountered: