Daniel Haven

Where in the composer.json do I add `mustangostang\spyc`?

> I found a workaround by adding this in nuxt.config.ts: > > ``` > build: { > optimization: { > runtimeChunk: true, > splitChunks: { > name: true, > cacheGroups:...

Wouldn't your Laravel application throw an error anyway if an interface wasn't applied correctly?

Looking into it. As a side-note, this seems like something that should error our in tests regardless of whether or not you use architecture testing.

After looking at the code, I believe one way to resolve this is to add a new `src/Expectation` method in this repository. ### Potential Implementation ```php /** * Asserts that...

```php $response = get('route')->assertOk(); $json = $response->json(); # some code to determine that the response json is tied to LaravelData ``` Correct me if I'm wrong, but response JSON always...

> Can you share the full test? Are you using `covers`? It is using `covers`. I will recreate one in a dummy repository later. If there is no problem with...

> Can you share the full test? Are you using `covers`? I've created a quick repo for demonstrating the issue: https://github.com/danielh-official/demonstrating-laravel-pest-mutation-testing-issue-with-models

The band-aid I set for this issue is the following: ```php /** * @pest-mutate-ignore */ protected $guarded = [ 'id', 'created_at', 'updated_at', ]; /** * @pest-mutate-ignore */ protected $hidden =...

As a bandaid, I would suggest putting a `// @phpstan-ignore-next-line` above the offending code. Read more: https://phpstan.org/user-guide/ignoring-errors#ignoring-in-configuration-file If it's a lot of code, you can ignore a regex of the...