Antoine Bluchet

We need the database to be up to read eloquent's metadata.

Not sure I understand the configuration, are all these resources on the same class?

Yes directly on the ApiProperty looks like a good option, directly inside canAccessAttributePostDenormalize. Because it's painful to add a new property maybe it'd be enough to just use the `extraProperties`?...

feel free to open a pr

I expect this is an issue from symfony? But it's weird, what property info extractor are registered on your project?

Could you help tracking this by checking values at https://github.com/api-platform/core/blob/main/src/Metadata/Property/Factory/PropertyInfoPropertyMetadataFactory.php#L48-L59 ? (remove your cache if you don't hit these lines) I need to know if this needs fixing in symfony...

since https://github.com/symfony/symfony/pull/57617 got merged, can you try https://github.com/api-platform/core/pull/6947 ?

My bad, we wanted to support php 8.2 only for v4.0.

Thanks!

Amazing contribution! Do you think that we can use `ApiPlatform\Metadata\Exception\AccessDeniedException` ? Indeed I'm trying to get rid of the `Symfony\Exception` namespace as its not compatible with Laravel.