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
We have an incorrect behavior regarding Activity: all methods of ActivityInterface classes are scanned and added as activity methods, instead of only registering methods with the ActivityMethod attribute only. This leads to even class constructors being included in the activity list.
Additional context
Despite the fact that the documentation everywhere instructs the user to use attributes to mark activity methods, there is a chance that not everyone followed this.
I propose to solve the problem in 2 stages:
First, we will inform the user that they are calling an activity method that is not marked with an attribute. We will immediately remove constructors and other magic methods from scanning.
After some time, we will completely disable the registration of activity methods without attributes.
The text was updated successfully, but these errors were encountered:
Describe the bug
We have an incorrect behavior regarding Activity: all methods of
ActivityInterface
classes are scanned and added as activity methods, instead of only registering methods with theActivityMethod
attribute only. This leads to even class constructors being included in the activity list.Additional context
Despite the fact that the documentation everywhere instructs the user to use attributes to mark activity methods, there is a chance that not everyone followed this.
I propose to solve the problem in 2 stages:
The text was updated successfully, but these errors were encountered: