* Followup work on setup github actions
* Coverage report & split `prod_lint`
* Add env
* Remove coverage report on azure pipelines
* Remove build step on lint
* remove coverage report on prod_test
* Use `ci-info` instead of `is-ci`
* Always enable `ENABLE_TEST_RESULTS` and `AST_COMPARE` on CI
* Standalone test and remove some env
* coverage report
* reduce matrix
* standalone test
* `ci-info`
* Remove token
* Disable `coverage` on azure pipelines
* use master version of codecov-action
* Link to master status
* fix prod lint
* Use boolean env
* Remove locv report
* Try lcov report
* pin `codecov-action` version, enable `verbose`
* azure coverage
* Name
* Trigger CI
* Use `basename`
* Trigger CI
* Try `runInBand`
* try `maxWorkers`
Co-authored-by: Georgii Dolzhykov <thorn.mailbox@gmail.com>
- upload coverage report (codecov) from azure pipelines
- only build `dist` once (`dist` is now shared between production jobs)
- run production tests on macOS (not sure why but it's faster than others)
- extract shareable steps
- remove travis/circle
* Fix spacing around badges
* Switch the npm downloads badge to weekly
I switched to a weekly statistic since it feels more immediate and “9M/m” is somewhat confusing.
There's a lot of demand for vue sfc (#2097). This introduces partial support for them: all the html is printed as is, except for the script and style tags which are printed using prettier. I believe that this should cover a lot of the use cases while being simple to support and if we want we can extend to more in the future.
I copy pasted the html parser used by vue (it's just a single 400 lines file) so that we don't run the chancesof conflicts. I'm also very conservative: I only print the style and script at the top level and for the lang attributes we support.
I expect this to be landable as is and provide value, review welcome :)
* Implement getSupportInfo() and use it for inference
* Add comment with source of languages.yml
* Fix build, pin semver
* Simplify test snapshots
* Remove stray 'type' property
* Fix parser being overwritten
* Don't infer unreleased parser from extension
* Add CLI and docs for support info
* Change badge to say “formatted”
“Styled” sounds like a CSS or CSS-like thing to me — Prettier is a code formatter
* Update code too
* Update the badge at the top too
* Reword badge to “code style: prettier”
* Add option to insert @format pragma if absent
prependPragma --> insertPragma
add tst dir, move stripBom, add to README, update snapshots
remove noise from test + update snapshots
use jest@test new functions, update docs, rerun snapshots
fix accidental upgrade to jest@test
update jest-docblock again to latest with strip()
updated snapshot
* updated snapshots
* revert jest dep change
* apply a trim to parsed comments
* remove empty object
* Revert "apply a trim to parsed comments"
This reverts commit 467f71ce5f4b4f8a1b5c4474ee0484bc96c92141.
* rerun snapshots with proper jest version
* pin jest-docblock to latest @test release
* comment out docs for new feature from readme
* remove leading newlines
* ensure blank line between docblock and rest of file
* remove backtick string
fisker Cheung