iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/integration/language_service_plugin
History
Vikram Subramanian 5c5c2ae405 fix(platform-server): setup NoopAnimationsModule in ServerModule by default (#15131) 
This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module.

Fixes #15098, #14784.

PR Close #15131
 		2017-03-17 16:21:51 -05:00
..
fixtures test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
project test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
scripts test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
tools test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
typescripts/2.3 test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
.gitignore test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
README.md test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00
package.json fix(platform-server): setup NoopAnimationsModule in ServerModule by default (#15131) 2017-03-17 16:21:51 -05:00
tsconfig.json test(language-service): test `@angular/language-service` can be loaded by tsserver.js (#14721) 2017-03-01 13:22:46 -08:00

README.md

Angular Language Service Test

This directory is an integration test for @angular/language-service to ensure that various versions of the server can be loaded in the supported versions of TypeScript's language service.

New supported version of TypeScript

To add a new supported version of TypeScript:

  1. Create directory in typescripts to hold the new version following the pattern of the other versions.
  2. Add the directory name to the end of the TYPESCRIPTS variable in the scripts/env.sh file.
  3. Run scripts/update_golden.sh to generate the expected files.
  4. Verify the expected output is reasonable by comparing to a known good output from a previous version.

Update golden files

If the expected output needs to be updated run scripts/update_golden.sh to update the expected output of the server.

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:

  1. Add the fixture base name (without the .json) to FIXTURES in scripts/env.sh.
  2. Run scripts/udpate_golden.sh to produce the expected output files.
  3. Hand validate the expected output is reasonable.