Interesting approach of basically providing a meta-layer on top of existing tools.
Do you have an example of how you inject context into the codemods? The approach we've taken at Grit is two-fold:
1. When something must be addressed (ex. `todo`), we have functions that wrap messages into the source code to ensure anyone sees the info until it's fixed. We pick up these messages automatically on our SaaS platform.
2. For non-blocking comments, we have a `log` function that any query can call to surface info into the result stream on the CLI + pull requests without it ending up in the final PR.
>4. all of today’s codemod libraries are for one language, so they are hard to orchestrate for a single project.
Do you have an example of how you inject context into the codemods? The approach we've taken at Grit is two-fold:
1. When something must be addressed (ex. `todo`), we have functions that wrap messages into the source code to ensure anyone sees the info until it's fixed. We pick up these messages automatically on our SaaS platform.
2. For non-blocking comments, we have a `log` function that any query can call to surface info into the result stream on the CLI + pull requests without it ending up in the final PR.
>4. all of today’s codemod libraries are for one language, so they are hard to orchestrate for a single project.
This isn't entirely true! Grit, my project, was built to be multi-language from the start: https://docs.grit.io/language/overview
[0] https://docs.grit.io/language/functions#todo