KapitanOczywisty

This is not react and key have to be accessible somehow to be any useful, for example to use with `morphdom`. Otherwise should be removed from types.

And another thing to change in `patch-package`... Completely removing `key` is wasteful, since it could be used with packages like `morphdom`, especially when somebody consciously adds `key` attribute to the...

> why not use `key.startsWith('on')` ? @adminy This was already present in code, but my guess is performance optimization or compatibility or no reason at all.

There is PR to fix this, but intelephense works only with `@`, but not with `$0`, so action from @bmewburn still will be required. https://github.com/mockery/mockery/pull/1126

@Sectimus Or you can add `.phpstorm.meta.php` file to own project, to have project-wide solution: ```

> I've tried many different implementations of the `.phpstorm.meta.php` file. Although Intelephense does state that it reads and supports these, I am still receiving `Expected type 'object'. Found 'string'`. I'm...

`class_exists` will suppress also method calls to this class? Idea is interesting, but will result for sure with angry bug reports :) I mean, following example is ridicules and probably...

@saippuakauppias Intelephense doesn't support that and probably will not in the near future. Other editors/analyzers may use non standard implementations e.g. [phpStorm](https://gist.github.com/discordier/ed4b9cba14652e7212f5), [Psalm](https://psalm.dev/docs/annotating_code/supported_annotations/#psalm-suppress-someissuename)

@ilyaguy Set `"intelephense.environment.phpVersion": "5.6.0"` and add `"mysql"` to `"intelephense.stubs"`

There is no such type in phpdoc, afaik this is non-standard type from psalm.