William Chargin 1c28c75e39

Check in example repo’s in-memory representation (#166) ...

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

2018-04-27 20:51:54 -07:00

..

jest

Move package json to root (#37)

2018-02-26 22:32:23 -08:00

env.js

Move package json to root (#37)

2018-02-26 22:32:23 -08:00

paths.js

Check in example repo’s in-memory representation (#166)

2018-04-27 20:51:54 -07:00

polyfills.js

Move package json to root (#37)

2018-02-26 22:32:23 -08:00

webpack.config.backend.js

Use isomorphic-fetch instead of node-fetch

2018-03-19 20:06:52 -07:00

webpack.config.dev.js

Move package json to root (#37)

2018-02-26 22:32:23 -08:00

webpack.config.prod.js

Move package json to root (#37)

2018-02-26 22:32:23 -08:00

webpackDevServer.config.js

Move package json to root (#37)

2018-02-26 22:32:23 -08:00