Open gsteel opened 2 years ago
Before going down this line, perhaps we could ask for psalm itself to have this sort of "stricter" defaults with a single flag? Maybe errorLevel="0"
? :P
/cc @orklah
Yeah, that'd be great, this has been suggested in Psalm issue tracker also: https://github.com/vimeo/psalm/issues/7630
/cc @AndrolGenhald
I'd like to propose these two as well.
https://psalm.dev/docs/running_psalm/configuration/#ensurearraystringoffsetsexist https://psalm.dev/docs/running_psalm/configuration/#ensurearrayintoffsetsexist
But I'd expect them to be enabled with the strictest option provided by https://github.com/vimeo/psalm/issues/7630
Thanks to @boesing, I recently discovered some psalm configuration options that'll be potentially helpful to improving code quality.
I'd like to start discussion about which of those options we should switch on or off by default for Laminas and Mezzio projects so that we can define a standard configuration.
Once a standard has been decided, it should be applied everywhere with an expanded baseline so that new code will need to pass a stricter set of requirements as enforced by CI.
To start discussion off, I'm thinking something like this:
Reference: https://psalm.dev/docs/running_psalm/configuration/
Perhaps, once decided, a template can be stored in the Laminas .github organisation repo?