Antoine Bluchet

I thought about this a little bit more and I think that we shouldn't cache the context. A few things may change the context between providers and we can't be...

sorry for the late answer I missed the comment, as the ContextBuilder is tight to Request I recommend that you do something like this: ``` // in a middleware, or...

Sometimes `read` is not called (on POST operations for example). But indeed, we may add a check and use the previously computed context.

:+1: you can target 3.4

Create a service provider I'm not sure how we're supposed to know what services to inject in the UserProcessor.

If you want both arguments to be properly injected you're missing something like: ``` $this->app->singleton(UserProcessor::class, function (Application $app) { return new UserProcessor( $app->make(\ApiPlatform\Laravel\Eloquent\State\ItemProvider::class), $app->make(\ApiPlatform\Laravel\Eloquent\State\RemoveProcessor::class), ); }); ```

don't hesitate to update the documentation thanks!

It's because it could not find identifiers? Context is reset for embed resources it's expected

The identifiers extractor is supposed to find the uri variables from the $originalData at https://github.com/api-platform/core/blob/v3.3.11/src/State/Processor/RespondProcessor.php#L115

please query our issues for that the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386) standard does not update embedded collection. https://datatracker.ietf.org/doc/html/rfc7386#appendix-A ``` ORIGINAL PATCH RESULT ------------------------------------------ ["a","b"] ["c","d"] ["c","d"] ```