-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Regenerating hydrators do not refresh them #29
Comments
@mirfilip good point. I think the simplest way would be to implement signing like Ocramius/ProxyManager#172 |
@mirfilip consider that I don't have time to fix this bug right now, so consider sending a PR after looking in the linked PR. |
@Ocramius I'll try to have a go, sure. |
Hey guys, we just hit the same issue. Any further news about this? |
@gonzaloserrano, I'll be looking at this this week(end), stay in touch |
Hi again, i found the root cause of my issue and i think it's not related. Somehow some (3) files from generated files stored in
I have changed those file permissions and i think now it works as expected. Thanks for your time. |
First of all, I'm not sure whether this is a bug, an expected behaviour or a missing feature, so please go easy :)
I try to use pre-generating hydrators feature and hook it up with my deployment system. I've created
generate.php
script with a snippet doing basically what documentation says (and it works fine). I, then, intend to use it withpre-autoload-dump
composer event script in order to achieve fresh hydrators for my objects every time I runcomposer install/update
(regardless if it's development or production env).The reason I want fresh hydrators every time is that the default values / attributes can easily change during development.
Because of a class existence check in
HydratorFactory::getHydratorClass()
,HydratorFactory
will not attempt to create a proxy class when it already exists. I think pre-generation is intended for production usage only, when classes are not meant to get changed (thus hydrators don't need refreshing). Anyway, removing this class existence check makes it fit my scenario. How do you feel aboutforceRefresh
kind of flag @Ocramius ?Alternatively, do you have any ideas how to work it around ?
The text was updated successfully, but these errors were encountered: