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

Add user preference to opt-in to renaming import paths #29385

Merged
merged 3 commits into from
Jan 15, 2019

Conversation

uniqueiniquity
Copy link
Contributor

Fixes #28677.
This PR adds a user preference which, if not set, returns the rename behavior on import paths to its state in 3.0.

@uniqueiniquity uniqueiniquity merged commit c5948bf into microsoft:master Jan 15, 2019
@uniqueiniquity uniqueiniquity deleted the renameImportPref branch January 15, 2019 18:30
uniqueiniquity added a commit that referenced this pull request Jan 31, 2019
<!--
Thank you for submitting a pull request!

Here's a checklist you might find useful.
* [ ] There is an associated issue that is labeled
  'Bug' or 'help wanted' or is in the Community milestone
* [ ] Code is up-to-date with the `master` branch
* [ ] You've successfully run `jake runtests` locally
* [ ] You've signed the CLA
* [ ] There are new or updated unit tests validating the change

Refer to CONTRIBUTING.MD for more details.
  https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md
-->

Fixes #29585.
#29314 and #29385 made it so their respective settings are only recognized when provided to the host as a whole.
This PR makes it so that the relevant settings for the preferences on the file override those of the preferences on the host.
@pie6k
Copy link

pie6k commented Mar 21, 2019

Is it released already?

@amcasey
Copy link
Member

amcasey commented Mar 25, 2019

@pie6k from the tags, it looks like it's in 2.4 RC, which is available here or on npm.

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

Successfully merging this pull request may close these issues.

4 participants