You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would appear that to invoke logging for a method even if its decorated with a logging aspect attribute has to be called externally via the instance of the dynamic object reference. This would be a huge limitation as it appears that internal method call that take place within the class itself never get their respective aspect invoked and thus never get logged as part of a call start. Or whatever other functionality you might introduce other than logging. This would mean that in order to use this framework one would have to change their architecture so that every single method gets called in reference to the dynamic instance of an object and can not call methods internally if they are expecting aspect based behavior to execute.
The text was updated successfully, but these errors were encountered:
@cas8180 I meant that your pull request is welcome)
But I am not sure how to achieve that behavior for internal methods since the "AOP magic" can work only with "dynamic". I agree this is the big limitation. But I think that AOP can be achieved simpler with just composition of functions without any AOP framework. (func1 >> func2 >> func3Logging >> func4)
It would appear that to invoke logging for a method even if its decorated with a logging aspect attribute has to be called externally via the instance of the dynamic object reference. This would be a huge limitation as it appears that internal method call that take place within the class itself never get their respective aspect invoked and thus never get logged as part of a call start. Or whatever other functionality you might introduce other than logging. This would mean that in order to use this framework one would have to change their architecture so that every single method gets called in reference to the dynamic instance of an object and can not call methods internally if they are expecting aspect based behavior to execute.
The text was updated successfully, but these errors were encountered: