-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
[Bug] initialization pointcut makes other advices not bound to target #425
Comments
Hello, thank you for reporting this. Unfortunately, initialization joinpoint is one of the most tricky, thus not reliable part of framework and requires to process all files with |
I'll try to have a look into this issue, maybe it isn't so complicated... |
It could be fixed with some workaround - call to other method in constructor. BTW. Your framework is awesome, thanks for you time! |
I have prepared bugfix for that issue. Pull request created. I have tested it in my sandbox project. Also I see that master branch has lot of changes wiht comparsion to 2.x branch. When do you plan make next release? |
No, it was used outside of class. |
I've reproduced this. But things are worse when using |
* origin/2.x: Fix constructor invocation to know about special parent class names, fix #425
Please, test 2.x or master branch to confirm that this issue is fixed now. |
If I add
initialization
pointcut to aspect it makes only this one executed.Also class is changed to
App\Example__AopProxied
(normally in methodInvocation I getApp\Example
).For
staticinitialization
it works ok - nothing wrong happens. But If I addinitialization
targeting same class as other advices it makes all those advices stop working - only initialization is executed.The text was updated successfully, but these errors were encountered: