Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Use explicit exports for formatters. #863

Merged

Conversation

DanielRosenwasser
Copy link
Contributor

Since all of the formatters are named Formatter, this is going to break in TypeScript 1.8 and we noticed it when nightlies weren't getting published.

@adidahiya
Copy link
Contributor

👍

reverse issue link: microsoft/TypeScript#6008

adidahiya added a commit that referenced this pull request Dec 10, 2015
…rExports

Use explicit exports for formatters.
@adidahiya adidahiya merged commit 810f855 into palantir:master Dec 10, 2015
@adidahiya adidahiya added this to the TSLint 3.2 milestone Dec 10, 2015
@DanielRosenwasser DanielRosenwasser deleted the fixAmbiguityInFormatterExports branch December 10, 2015 01:15
@DanielRosenwasser
Copy link
Contributor Author

🎉 Any clue when this'll make it's way to the tslint@next?

@jkillian
Copy link
Contributor

We definitely don't want to be breaking TS nightly builds! A next release sometime tomorrow should be doable

@adidahiya
Copy link
Contributor

@DanielRosenwasser just published 3.2.0-dev.2 to tslint@next.

@DanielRosenwasser
Copy link
Contributor Author

Awesome! I'll give it a shot now.

@DanielRosenwasser
Copy link
Contributor Author

Everything seems to be working. Given that, typescript@next should be published at later tonight. Thanks guys!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants