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

do we need filters as a top-level plugin type? #10

Open
bttmly opened this issue Oct 24, 2018 · 0 comments
Open

do we need filters as a top-level plugin type? #10

bttmly opened this issue Oct 24, 2018 · 0 comments

Comments

@bttmly
Copy link
Owner

bttmly commented Oct 24, 2018

It seems like most filters are only relevant to specific mutators (e.g. the tweak-string mutator can know to avoid tweaking require("thing")) – is it necessary to have a top level filter plugin?

Since they are already supported and seem (potentially) useful probably won't remove them entirely, but all of the current filters seem like they should go into mutators.

NOTE: it may be that we want to change where filters get applied. There should probably be a way to stop recursive descent and move on if a node meets certain qualities.

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