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
This means you can patch multiple functions in the same way with the same code, but there's no way of knowing the name of the actual function that is running. This is useful if you want to add it to the raised monitoring event.
Passing the function name through to the function callbacks as an additional (last) parameter provides access to the name of the function without breaking existing code, eg:
@tunniclm Any view on the addition of the patched function name as a new last parameter passed to the supplied before and after callbacks?
Note that this only applies to aspect.before(), aspect.after() and aspect.around(). The aspect.aroundCallback() call doesn't take a function name - you should already have that from a previous call to aspect.before() or aspect.around().
The aspects patching framework allows you to specify an array of function names to patch. eg. for aspect.around:
This means you can patch multiple functions in the same way with the same code, but there's no way of knowing the name of the actual function that is running. This is useful if you want to add it to the raised monitoring event.
Passing the function name through to the function callbacks as an additional (last) parameter provides access to the name of the function without breaking existing code, eg:
The text was updated successfully, but these errors were encountered: