Skip to content
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

[feature] custom filters for pros #503

Open
arvitus opened this issue Oct 8, 2024 · 0 comments
Open

[feature] custom filters for pros #503

arvitus opened this issue Oct 8, 2024 · 0 comments

Comments

@arvitus
Copy link
Contributor

arvitus commented Oct 8, 2024

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant