Juliette
Juliette
> Without the ability to reliably infer the type of a variable, any attempt beyond this basic scenario just risks false positives or miss things. ... I think it's worth...
> This was referring to the official release [announcement](https://www.php.net/releases/8.3/en.php), not upgrading doc. Other changes I was researching appear on that announcement. I see. In my experience, the release announcement generally...
@afilina What's your assessment on "is it worth spending time on writing and maintaining a sniff for this ?"
Okay, let's, but also let's make this _low priority_ as the Phar extension is only really used by CLI tools, so is not a popular extension for packages in general.
@sabernhardt Thank you for coming up with those examples. Seeing the examples you posted above.... I realize my remark about using existing WP globals was wrong, as it would lead...
> ... to make a fully operative no-mbstring suite, we need to tag all the tests that are requiring mbstring to exclude them selectively > > I've added two groups...
> @jrfnl the idea is to group them to be able to exclude them in certain testing protocols to provide a cleaner testing report that focus on tests that are...
> ... it's also easy to sniff, for the most part (`Syntax Variations`). Agreed. This one definitely seems viable to write a sniff for. Category: `MethodUse` ;-)
@rodrigoprimo Nice find. Low priority to fix as it is uncommon for short open tags (not echo) to be enabled, let alone used. > I believe the sniff should be...
@rodrigoprimo Good catch, still low prio. Having said that, might be good to check if the `Generic.PHP.DisallowShortOpenTag` sniff fixer checks whether there is a whitespace char after the short open...