Philzen

> as it's a breaking change with fallback @wing328 BTW – how can i add labels to my own existing PRs or issues? I've seen we have a label for...

@segunadebayo Many thanks for merging! Can you say when 2.8.3 is going to be published so this (along with other improvements such as #8104) will become available?

> `isDisabled` insted of `disabled` worked for me @coxato Worked to do what exactly? If you refer to just disabling the button, surely `isDisabled` works. That is not the scope...

Open, yes absolutely, i love contributing to open source. Unfortunately i'm head over heels in the middle of two other projects that i'm commited to, so for the moment i'm...

I retried the recipe with `application.properties` on the same project. I had just converted to YAML before i ran the recipe and it worked fine with `.properties`, great stuff. Closely...

While the original issue was only introducing an additional / duplicated dependency, i now found an example where it leaves the project in a non-compiling state after running the recipe....

Confirming this issue on Java+JUnit5. Thanks @ross-paypay for pointing out the workaround. Another workaround is to use injected field, which unfortunately reports that it is deprecated for removal in v5,...

@RomainPruvostMHH @wing328 > I'm done other tests and in fact, it doesn't work in my case because I use $ref in items. I was able to reproduce this behavior on...

@wing328 Reviewers and contributors are going to like this :) Unfortunately Windows and CircleCI checks are still far >10m, however this helps with time needed for local test suite execution.

> for windows, we can improve that with another PR later. @wing328 i checked the actions' log, the test in question also fails quickly as expected there – however the...