When updating tree-sitter dependencies, there might be changes to the grammars that we might need to take into account.
Sometimes they are new features, so they don't break our current code. Sometimes they might contain breaking changes too, so we need a way to validate them.
We could write a script that:
- Clones a big repository such as mozilla-central;
- Runs RCA, storing the metrics in JSON files;
- Applies the tree-sitter language update;
- Runs RCA again, storing the metrics in a separate set of JSON files;
- Generates an explorable diff of the JSON files.
If the diff is empty, or all the changes in the diff makes sense, then we can apply the tree-sitter update.
If some of the changes in the diff are bad, we can't apply the tree-sitter update and we need to debug what's wrong.
When updating tree-sitter dependencies, there might be changes to the grammars that we might need to take into account.
Sometimes they are new features, so they don't break our current code. Sometimes they might contain breaking changes too, so we need a way to validate them.
We could write a script that:
If the diff is empty, or all the changes in the diff makes sense, then we can apply the tree-sitter update.
If some of the changes in the diff are bad, we can't apply the tree-sitter update and we need to debug what's wrong.