Lucas Bremgartner

This is not quite true, you always have the possibility to use `go get -u github.com/matryer/is@master`, which will add `github.com/matryer/is v1.4.1-0.20220516095740-02e4121244e0` to your go.mod, but I agree, it is better,...

I like this and I wanted to have something like this in the past myself. It is especially useful in combination with `NewRelaxed`.

@jli-cparta Can you provide an example, how you would use this new functionality. I can see the value e.g. if one wants to print additional debug information in the case...

First of all, I am not the maintainer of this package but only a frequent user myself, so in the end, you will not have to convince me but @matryer....

But if you only care about the relevant error, why don't you write the code like this: ```Go func Test_Sample_Parses_OK(t *testing.T) { is := is.New(t) f, err := os.Open("test.sample.data") is.NoErr(err)...

This is not yet ready, see my [comment](https://github.com/magnusbaeck/logstash-filter-verifier/issues/147#issuecomment-956084012).

This one is related to https://github.com/elastic/logstash/issues/1645. The problem is, that back in the days, the escaping in the Logstash config format was not available. Since https://github.com/elastic/logstash/pull/7442, there is a way...

I just learned, that the logstash file input does support multiple `mode` (https://www.elastic.co/guide/en/logstash/current/plugins-inputs-file.html#plugins-inputs-file-mode), one being `read` (instead of `tail`). This feature was introduced 3 years ago and did not exist...

I quickly check since when the above mentioned `mode` feature in the `file` input is present. May tests show, that it is present at least from version 6.7.2 as well...

I created a PR to fix this issue. While working on the PR, I realized a nasty detail about yaml. ```yaml - > { "before": "hello" } ``` translates to...