Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use correct extension for typescript fixtures #10014

Merged
merged 4 commits into from Jul 15, 2019
Merged

Conversation

@danez
Copy link
Member

@danez danez commented May 23, 2019

Q                       A
Fixed Issues?
Patch: Bug Fix? n
Major: Breaking Change? n
Minor: New Feature? n
Tests Added + Pass? Yes
Documentation PR Link
Any Dependency Changes?
License MIT

Simply batch changed all extensions for typescript fixtures to ts or tsx.

@babel-bot
Copy link
Collaborator

@babel-bot babel-bot commented May 23, 2019

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/11148/

@nicolo-ribaudo nicolo-ribaudo force-pushed the danez:ts-ext branch from de6775a to 8a206c9 Jul 15, 2019
@nicolo-ribaudo nicolo-ribaudo merged commit d8da63c into babel:master Jul 15, 2019
4 checks passed
4 checks passed
@babel-bot
babel/repl REPL preview is available
Details
ci/circleci Your tests passed on CircleCI!
Details
@codecov
codecov/project 87.62% (target 80%)
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@danez danez deleted the danez:ts-ext branch Jul 16, 2019
AdamRamberg added a commit to AdamRamberg/babel that referenced this pull request Jul 17, 2019
* Use correct extension for typescript fixtures

* Change transform fixtures

* Adjust editorconfig for ts files

* Rename new tests

Co-authored-by: Nicolò Ribaudo (nicolo.ribaudo@gmail.com)
@lock lock bot added the outdated label Oct 15, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants