Alies Lapatsin

@eusonlito From what I found, the issue caused by `vendor/psalm/plugin-laravel/cache/models.stubphp` file (available after running psalm). Previously this file was empty, but we fixed it in https://github.com/psalm/psalm-plugin-laravel/releases/tag/v2.1.1, so the latest working...

for anyone looking for a maintained alternative, there is a fork that supports L11, fully compatible with this package and has some features on the top: https://github.com/InteractionDesignFoundation/laravel-geoip a super simple...

It's fixed on a fork: https://github.com/koot-labs/telegram-bot-dialogs (more stable, better docs, actively maintained)

It's fixed on a fork: https://github.com/koot-labs/telegram-bot-dialogs (more stable, better docs, actively maintained)

@eric2100 @sigaev-pro I've forked this package, updated it to support Telegram SDK v3, Laravel 9 (now it's optional dependency), PHP8.0+. The package is already stable, with tests and basic docs,...

as temporary solution you can change your WP constant DB_CHARSET to : ``` php define('DB_CHARSET', 'utf8mb4'); ``` or ``` php define('DB_CHARSET', 'utf8mb4_unicode_ci'); ```

Hey @Rizky92 what is the laravel plugin version you use? in [v2.6.0](https://github.com/psalm/psalm-plugin-laravel/releases/tag/v2.6.0) we fixed a major issue that leaded to high memory consumption. This plugin version works with Laravel ^9.2:...

Hey @Rizky92 Can you please try to use `1.x` branch of the package? like: ```json "psalm/plugin-laravel": "dev-1.x as v1.6.3" ``` I just applied the same performance fix as I did...

UPD: the fix is released as v1.6.3. Please ping me here if something is broken on this version.

@eusonlito >The failed tests are my bad? I don't think so. Codeception tests failed due to Psalm changes (a new output), Laravel projects tests failed due to a flag to...