scala-validation/ holds the first version of the Babel Validator, written in Scala. It has not been maintained since the Python test suite took over, its sbt diff / sbt validate subcommands duplicate what the pytest suite and Babel itself now do, and README.md and CLAUDE.md both describe it as legacy and unmaintained.
Meanwhile it still costs us something: .github/workflows/scala.yml is a live workflow (currently workflow_dispatch only, with the push and pull_request triggers commented out), and every reader of the repository has to work out that the directory is not part of the current tool.
Proposed:
- Delete
scala-validation/ and .github/workflows/scala.yml.
- Drop the "The Babel Validator in Scala" section from README.md and the
scala-validation/ entry from CLAUDE.md.
- The history stays in git, so anyone who needs the Scala implementation can recover it from the tag or commit that precedes the deletion.
Worth confirming before doing it: that nobody is still running the Scala diff tool against Babel outputs, and that its diff output format is not an input to anything downstream.
scala-validation/holds the first version of the Babel Validator, written in Scala. It has not been maintained since the Python test suite took over, itssbt diff/sbt validatesubcommands duplicate what the pytest suite and Babel itself now do, and README.md and CLAUDE.md both describe it as legacy and unmaintained.Meanwhile it still costs us something:
.github/workflows/scala.ymlis a live workflow (currentlyworkflow_dispatchonly, with the push and pull_request triggers commented out), and every reader of the repository has to work out that the directory is not part of the current tool.Proposed:
scala-validation/and.github/workflows/scala.yml.scala-validation/entry from CLAUDE.md.Worth confirming before doing it: that nobody is still running the Scala diff tool against Babel outputs, and that its diff output format is not an input to anything downstream.