While the CLI was still in the tools repo, we were limited in the version of oclif that could be used as there was a single version of every dependency shared by every package in the repository (since we had a singular Bazel source for it) and the devtools packages required a very old version of oclif due to flipper. Now that the CLI is in its own package, we should update to a modern version of oclif. To do this we'll need to:
- Write better tests for the current cli
- Could do this within Bazel (as oclif's testing framework may not be able to handle the amount of logic we need to test in the cli) by creating a local binary target (like we have done in some other repositories) and then having dedicated test packages to run the CLI to compile content, validate content, and export XLRs
- Do the update and migration work
- Run the test suite against the changes
While the CLI was still in the tools repo, we were limited in the version of oclif that could be used as there was a single version of every dependency shared by every package in the repository (since we had a singular Bazel source for it) and the devtools packages required a very old version of oclif due to flipper. Now that the CLI is in its own package, we should update to a modern version of oclif. To do this we'll need to: