* Run `format()` in test function
* Wrap `test`s in `describe`
* Update tests_config/run_spec.js
Co-Authored-By: Georgii Dolzhykov <thorn.mailbox@gmail.com>
Co-authored-by: Georgii Dolzhykov <thorn.mailbox@gmail.com>
* feat: add new parser `babel-ts` to parse TypeScript syntaxes via Babel
* docs: document parser babel-ts
* chore: enable babel-ts in markdown and worker.js
* verify all TS tests against babel-ts except disabled by disableBabelTS
* support for TSDeclareMethod; fix abstract properties and methods
* fix embedded angular templates and styles
* fix TSImportType
* simplify babel options combinations
* fix method decorators
* fix ranges
* work around loc inconsistencies for SequenceExpression
* don't print trailing comma in type parameters (unsupported in TS < 3.3)
* preserve quotes for class properties
* align printing of single-parameter functions
* fix comments in degenerate single-element unions and intersections
* fix comments for methods
* fix comments for mapped types
* edit docs, change 'since' to 2.0.0
* add changelog
* fix code sample on playground
* update snapshots after rebase
Co-authored-by: Georgii Dolzhykov <thorn.mailbox@gmail.com>
* chore: upgrade Jest
* chore: update snapshots
* chore: lock down babel dependency using invalid syntax
* 2 args to test.skip
* use jest 22 for now
* Revert "2 args to test.skip"
This reverts commit 691fdc3f99e320f2303958f2b503f7b4c93fa455.
* remove snapshot name from matcher
* fix standalone tests skips
* Added prettier layout for class extends and implements
* Added prettier layout for class extends and implements, fix with keeping it in online if it fits
* Added prettier layout for class extends and implements, fixed tests as a side change
* Extends implements comments in same line fix
* Extends implements comments in same line without ugly workaround
* added empty line to test typescript_class/extends_implements.ts
* If only one extends keep old behaviour
* Removed console logs
We used to be very naive and just push all the comments at the top of the class, but it's very brute force (and breaks some flow annotations inside of fb) so we can do better :)
* Verify parsers against same snapshot
- Reworked run_spec, now accepts 3th optional array argument for
additional parsers to verify against
- Merged duplicate run_spec configs
- Removed duplicate snapshot data
* Formatted run_spec.js with prettier
* Fixed node4 incompatibility
* Revert "Remove mutation in `printBinaryishExpressions` (#1067)"
This reverts commit e7312ad7b2.
* Revert "Make it clear what parser was used in each snapshot (#1068)"
This reverts commit 4f7ae4815b.
* WIP immediate feedback
* typescript parser is drop-in replacement for flow parser
* Add new TypeScript Parser snapshots where drop-in replacement possible
* Snapshot updates after rebasing
* Remove unnecessary stripping of properties on TypeScript parser AST
* Remove annotated issues
* Move TS dependencies to dev for now
Instead of trying to figure out a complicated way to preserve their correct position, it's easier to just migrate those comments before the class.
Fixes#693Fixes#694
