laravel - How can I differentiate the exposed properties on the item and the collection routes? - Stack Overflow

admin管理员组

文章数量:1336304

I have been API platform with Symfony since the first beta version.

I am now using it with Laravel and I am trying to differentiate the properties (aka Eloquent attributes) that are exposed on the item and collection routes. Using the $hidden property seems to be the only way, and it feels a bit limited. I even tried to decorate the CollectionProvider to dynamically call setHidden on all the models of the collection, but it is too late in the process since it has already been extracted ahead of the provider. Also, decorating the provider is not technically possible unless the new provider is also manually declared on each operation of all resources because the default value for the provider in the Operation attribute is hardcoded and does not seem to come from the container.

Using an output DTO would be one way to achieve that, but I'm hoping I could go without the extra work of defining custom DTOs and providers and manually creating a new Paginator for collection routes just for this issue (also, the hydra attributes are messed up when using DTOs).

What thing similar to the normalizationContext with the Laravel version of API platform can I use to differentiate the Eloquent attributes that are exposed?

I have been API platform with Symfony since the first beta version.

I am now using it with Laravel and I am trying to differentiate the properties (aka Eloquent attributes) that are exposed on the item and collection routes. Using the $hidden property seems to be the only way, and it feels a bit limited. I even tried to decorate the CollectionProvider to dynamically call setHidden on all the models of the collection, but it is too late in the process since it has already been extracted ahead of the provider. Also, decorating the provider is not technically possible unless the new provider is also manually declared on each operation of all resources because the default value for the provider in the Operation attribute is hardcoded and does not seem to come from the container.

Using an output DTO would be one way to achieve that, but I'm hoping I could go without the extra work of defining custom DTOs and providers and manually creating a new Paginator for collection routes just for this issue (also, the hydra attributes are messed up when using DTOs).

What thing similar to the normalizationContext with the Laravel version of API platform can I use to differentiate the Eloquent attributes that are exposed?

• laravel
• symfony
• api-platform

Share Improve this question Follow edited Nov 25, 2024 at 5:44 DarkBee 15.5k88 gold badges7272 silver badges117117 bronze badges asked Nov 19, 2024 at 23:39 Philippe CARLEPhilippe CARLE 57144 silver badges1919 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

I figured out how to define the properties that I want to expose on each route.

new GetCollection(
    normalizationContext: [AbstractNormalizer::IGNORED_ATTRIBUTES => [
        'hidden_property_1',
        'hidden_property_2',
    ]],
),
// or

new GetCollection(
    normalizationContext: [AbstractNormalizer::ATTRIBUTES => [
        'property_1',
        'property_2',
    ]],
),

It works, but it is not reflected in the Open API documentation. I feel like it's more of a workaround than an actual solution.

本文标签： laravelHow can I differentiate the exposed properties on the item and the collection routesStack Overflow