@dmohns I checked phpstan.neon file and the level is set to 1. composer run larastan did not throw any errors but updating the level to 2 shows some errors. I'm working to address those errors, I wanted to let you that it was set to 1 instead of 2.

@dmohns I checked phpstan.neon file and the level is set to 1. composer run larastan did not throw any errors but updating the level to 2 shows some errors. I'm working to address those errors, I wanted to let you that it was set to 1 instead of 2.

Yes, this is correct 👍 To provide some context: Ultimately, our goal is to have Larastan set to level 10. However, because going from 0 to 10 requires massive refactoring, we decided to steadily move through Larastan levels, one at a time. We had previously managed to enable it on level 1, see here: #248

We also, added an "optional" CI step that checks Larastan on the next level, i.e. 2 currently, see https://github.com/EnAccess/micropowermanager/pull/410/files

What I would be expecting here, would be one (or multiple) Pull Requests that fix the issues reported by Larastan level 2. Once all are done, the optional Larastan (next) step on the CI should pass without errors. Once this has been achieved, we can dump the Larastan level in phpstan.neon.

Reopening, as it was closed by mistake. He are still not fully on level 2 yet 😉

@dmohns good catch!