4c63e6ba04
These were getting included in the @angular/localize package. Instead, patch the upstream files to work with TS typeRoots option See bazelbuild/rules_nodejs#1033 PR Close #33176 |
||
|---|---|---|
| .. | ||
| goldens | ||
| project | ||
| .gitignore | ||
| README.md | ||
| generate.ts | ||
| matcher.ts | ||
| package.json | ||
| test.ts | ||
| tsclient.ts | ||
| tsconfig.json | ||
| yarn.lock | ||
README.md
Angular Language Service Test
This directory is an integration test for @angular/language-service to ensure
that the language service works correctly as a tsserver plugin.
To use the tests:
- Use
yarn installto install all dependencies in this directory and in the Angular repo root directory. - Build an Angular distribution with
yarn build-dist. This needs to be done after changes to Angular, but not after changes to integration tests. This is an expensive build. - In this directory, run the integration tests with
yarn test.
Update golden files
If the expected output needs to be updated, run yarn golden my-golden.json, replacing
my-golden.json with the golden file to be updated. Do not qualify the file with a directory path.
See generate.ts for more information.
Adding a new fixture
Currently there is no automated way to produce a new fixture. The way the
current fixtures were created was to hack a version of tsserver.js to write the
commands from VSCode to a file while performing the operation to be tested.
I also hand modified the input to remove superfluous request.
Once a new fixture is created:
- Add the fixture name to
goldens/ - Run
yarn golden my-golden.json, replacingmy-golden.jsonwith the new fixture name, to produce the expected output files. - Hand validate that the expected output is reasonable.