1c28c75e39
Summary: Two reasons for this. First, we want tests to be able to operate on this data without having to generate repositories via `git(1)`. (Doing that is slow, and requires a Git installation, and makes it less clear that the tests are correctly isolated/provides more surface area for something to go wrong.) Second, in general plugins will need a canonical source of test data, so setting/continuing this precedent is a good thing. Test Plan: Observe that the old Jest snapshot must be equivalent to the new JSON one, because the test criterion in `loadRepository.test.js` changed and the test still passes. Then, run `loadRepositoryTest.sh` and note that it passes; change the `example-git.json` file and note that the test fails when re-run; then, run the test with `--updateSnapshot` and watch it magically revert your changes. wchargin-branch: check-in-git-repo |
||
|---|---|---|
| .. | ||
| jest | ||
| env.js | ||
| paths.js | ||
| polyfills.js | ||
| webpack.config.backend.js | ||
| webpack.config.dev.js | ||
| webpack.config.prod.js | ||
| webpackDevServer.config.js | ||