Closed disaster37 closed 4 years ago
Thanks for the PR, and sorry for the slow response. I glanced through the patch and it looked reasonably okay. I hope I can review it thoroughly during the coming week.
Any news ? There are still somethink I need to fix ?
Sorry, I've just been swamped with other things. I'll get to it. (Note that your branch conflicts with master, so in the meantime you can resolve that.)
I am so sorry, but how I can found the conflict in testcase/testcase.go
?
I am so sorry, but how I can found the conflict in testcase/testcase.go?
@langoureaux-s, I'm not sure what you mean. If you merge the PR branch with the master branch I'd expect you to get a merge conflict in testcase/testcase.go. The conflicting lines will be visible with the usual conflict markers inside the file.
Thanks! I'll push a follow-up commit to fix up typos and a few minor things. When I have time I'll push another commit that removes the dot notation support since it, as I said, is ambiguous. People should be able to have fields with dots in the names without getting into trouble with LFV.
YAML support is really nice and a great addition to LFV. Is it possible to cut a release with this new feature so I can add it to our CI pipeline?
Thanks.
Once the follow-up PR (#72) has been merged I'll make a release as soon as I can.
Once the follow-up PR (#72) has been merged I'll make a release as soon as I can.
1.6.0 is available now.
Add some enhances:
log.file.path
"log.file.path": "/tmp/test.log"
is equivalent to"log": {"file": {"path": "/tmp/test.log"}}
.json_lines
codecs to write test in easy way:{"log.file.path": "/tmp/test.log"}
is equivalent to{"log": {"file": {"path": "/tmp/test.log"}}}
.I add some unit test and fix readme.