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
The custom filters are really great! But one thing that would make them even greater, especially for advanced users, would be to somehow allow the sharing of variables between the before(), filter()/apply(), after() functions.
A "simple" way to allow this would be to put all of this in a class. So in the groovy script, instead of writing functions, one would create a class called e.g. Script. MCASelector then initializes this class without arguments and calls the before, after, filter, apply methods of the object. This way variables could be shared between the different methods, allowing for shorter code etc. Also, the class doesn't have to be initialized, all static fields and methods would already suffice.
I'd love seeing this in the app!
The text was updated successfully, but these errors were encountered:
The custom filters are really great! But one thing that would make them even greater, especially for advanced users, would be to somehow allow the sharing of variables between the
before()
,filter()
/apply()
,after()
functions.A "simple" way to allow this would be to put all of this in a class. So in the groovy script, instead of writing functions, one would create a class called e.g.
Script
. MCASelector then initializes this class without arguments and calls the before, after, filter, apply methods of the object. This way variables could be shared between the different methods, allowing for shorter code etc. Also, the class doesn't have to be initialized, all static fields and methods would already suffice.I'd love seeing this in the app!
The text was updated successfully, but these errors were encountered: