Sébastien Alfaiate

@psihius can you please share a screenshot of how i looks like when we embed a data table in a form?

Benchmark is running on a Symfony project using Annotations or Attributes? And do you have a benchmark on Symfony 7.0 where all deprecation checks have been removed?

@DannyvdSluijs 6.0.0 was released on 30th July https://github.com/jsonrainbow/json-schema/releases

Thanks for the information. I wish we could have a way to disable formulas globally. It feels a bit cumbersome to override the default value binder in every export that...

@finnef can you please resolve conflicts in that PR?

Hi @kubawerlos, Is it related to this bug: https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/issues/8515? Do your fix also fixes the issue with `get()`?

Just created that PR to reproduce the issue: https://github.com/laravel/pint/pull/353

I suspect `nikic/php-parser` to be the root cause of that issue. It was upgraded to `5.4.0` in Pint `1.19.0`: https://github.com/laravel/pint/commit/2128bf584f5bfe9dc303e524dc75674e0cf7ce63 And in the changelog I can find something related to...

The issue may come from one of those package upgraded between Laravel Pint 1.18.3 and 1.19.0: ``` "name": "larastan/larastan", "version": "v2.9.11", "version": "v2.9.12", "name": "phpstan/phpstan", "version": "1.12.11", "version": "1.12.13", "name":...

If I do: ```php Route::put('/customers/{customer}', [CustomerController::class, 'update']); Route::patch('/customers/{customer}', [CustomerController::class, 'update']); ``` The result is correct:  Previous result is also what I expect when I do: ```php Route::match(['put', 'patch'], '/customers/{customer}',...