Roman Mitasov

UP. Although I solved this issue by safe dereferencing, the need in using `?.` operator makes tests dirty and freaks me out. Is it even possible to make fail fast...

Maybe related to #1543

Just found out this amazing plugin and very exited to use it. But lack of this feature is really slowing down all the process. Hope It will be revisited soon...

Seems like I've found the cause. This works: ```kt assertThatJson("""[{"id": 123, "name": "abc"}, {"id": 432}]""") .isArray() .filteredOn("id", BigDecimal(123)) .first() .node("name") .isEqualTo(value("abc")) ```

I think such `BigDecimal` thing still counts as a bug. Also it's obvious that assertion error message is a bit unclear

1. I think it is possible to tweak assertions with BigDecimal by making custom type for `ACTUAL` and overriding equals so it will accept integers. 2. Yep, official AssertJ documentation...

Just noticed that when using `filteredOn` on an POJO list then message containing something like `[Filtered on ...]` is added to error report. I think this is what missing.

For me it doesn't really matter where this enhancement would land - in `buildHealth` task or in `reason`. When I open a "bad" project, I need to get a report...

Hi again, sorry for lack of clearness, I'll try to explain better. #### How it works now ``` INFO request didn't match expectation because: INFO didn't match expectation because: ......

And another waaay more powerful improvement is possible To get rid of repeating response JSON info, it can be separated out into new message: ``` // INSTEAD OF TRACE request...