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

Default path includes/excludes should not be used for remediation codemods #761

Closed
drdavella opened this issue Jul 30, 2024 · 0 comments · Fixed by #780
Closed

Default path includes/excludes should not be used for remediation codemods #761

drdavella opened this issue Jul 30, 2024 · 0 comments · Fixed by #780
Assignees

Comments

@drdavella
Copy link
Member

See the spec update: pixee/codemodder-specs#37

We should not make assumptions about default path inclusion/exclusion behavior for codemods that remediate tool results. These tools have their own defaults and/or configuration so codemods should simply respect whatever the tool reports. This behavior can still be overridden with --path-include or --path-exclude: the critical point is that we should not impose defaults on these types of codemods.

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

Successfully merging a pull request may close this issue.

1 participant