Completely Custom Resource

If you were creating this tutorial on custom resources for api-platform version 2.7 would you change anything significant? I'm asking since I'm currently trying to upgrade an (fully working) app from php7.4/symfony4.4/api-platform2.6 to php8.1/symfony5.4/api-platform2.7 and all my routes work except for the custom routes where I get a 404 not found exception. Following these videos I think I have everything necessary in the various places (and I also used the automatic upgrade script provided by api-platform) but I'm left scratching my head as to why the routes can't be found. Many thanks!

A little more info: changing

/**
 * @ApiResource(
 *   collectionOperations={
 *     "get_details"={
 *       "method"="GET",
 *       "path"="/details",
 *       "controller"=DetailsController::class,
 *       "normalization_context"={"groups"={"mock"}},
 *     }
 *   },
 *   itemOperations={"get"}
 * )
 */

to

#[ApiResource(operations: [new Get(), new GetCollection(uriTemplate: '/details', controller: DetailsController::class, normalizationContext: ['groups' => ['mock']])])]

makes the difference between the route being found or not, with the annotation version being the working one and the attribute one being the non-working version. In order for this to work I need to have metadata_backward_compatibility_layer: true set in api_platform.yaml

hallo,
i try to find a way to use LazyString as at 1:51,
so I create a property fakeName in user (the property is not in the serializazion group for the collection)

private ?string $fakeName = null;
public function getFakeName() : ?string
{
  return $this->fakeName;
}
public function setFakeName(?\Stringable $fakeName) : User
{
    $this->fakeName = $fakeName;
    return $this;
}

than in postLaod event i have done this

$bio = LazyString::fromCallable([$this, 'callback']
);
$user->setFakeName($bio);

and than i create the method itself

public function callback()
{
    dump('here i m');
    return 'ffffff';
}

but when i run http://localhost/api/users
all the dumps appears
so maybe i m not using it correctly?
can you suggest me a better way?

I am finding a couple of issues when applying this to graphql. I will report where I believe appropriate.

It seems that naming an Entity, or at least an ApiResource, with a name in plural is not a good idea as far as graphql is concerned.

When I enabled graphql I could not find the collection query for DailyStats. After I checked all else, I attempted to change the name of the Entity to DailyStat and voila! the collection query was where it shoud be. Of course, I changed all else from DailyStats to DailyStat.

API-Platform by default seem to assume that ApiResource name are singular and automatically pluralizes it to get the name of the collection query. As it got queries with the same name, it dropped one of them. Or so I believe.

Hey, everyone!

It seems that, at least in API Platform 2.6.5, adding @ApiResource() is not enough, since it requires to explicitly mark the identifier for the resource. So, you'll get an error like this:

No identifier defined in "App\Entity\DailyStats". You should add #[\ApiPlatform\Core\Annotation\ApiProperty(identifier: true)]" on the property identifying the resource.

By adding the following @ApiProperty(identifier=true) to the property that you want to uniquely identify the resource, the problem is solved.

In this case I added to the date property, since we're talking about <b>daily</b> stats:

`/**

• @ApiProperty(identifier=true)
  */
  public $date;
  `

Hope it helps!

Cheers!

How can I Unit Test the API in a stand alone Symfony Bundle?

Hello.

I have added a completely new Custom Resource, which gets data from an external service. Now I want to show this resource on another Entity based on its @id. How can I do that? I tried creating a new CustomResource($id) object but it doesn't go through the CustomDataProvider I wrote for it.
Thanks