-
-
Notifications
You must be signed in to change notification settings - Fork 888
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache not updated when entity annotation is changed #2644
Comments
Probably related to #2629... @teohhanhui can you take a look? Maybe should we revert this patch until it is properly tested and "edge cases" (this one is a basic case) are handled properly. |
This is even more related to #2593 and it's not easy to take a decision that will not have an impact. |
I prefer to favor DX than performance in dev env. |
|
Okay, I was mistaken. Symfony does not use cache in PropertyAccess: https://github.com/symfony/symfony/blob/v4.2.4/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/FrameworkExtension.php#L1680-L1688 So @dunglas is right, we have to revert. |
So we are back at square 1 with a lot of things to improve performance as it's so poor right now it's a also DX problem. |
@bastnic Unfortunately, yeah... |
About this case you can still use |
@bastnic in the meantime you can set |
If I remember correctly, the main issues are:
|
I'll look into it. |
Closing as it's been reverted in #2648, but I'll look into #2644 (comment) |
This morning, I started a new project with API Platform v2.4, and almost from scratch, I had to clear the cache to get my API documentation updated.
Steps to reproduce
Create a new Symfony application api-platform-issue
symfony new --full api-platform-issue
.Go to this new project (
cd api-platform-issue
).Install API platform by using
composer req api
.Install embedded web server
composer req server
and start itbin/console server:run
.Open API doc: http://localhost:8000/api
Create an entity Pizza:
Refresh your API doc, you don't see any change.
Delete your cache (
rm -rf var/cache
).API is updated.
Further steps
If you delete the annotation and update cache, you'll see no change.
Environment details
Bug reproduced:
The text was updated successfully, but these errors were encountered: