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

Editor configuration support based on a tsconfig.json naming convention. #2870

Closed
niemyjski opened this issue Apr 22, 2015 · 1 comment
Closed
Labels
Out of Scope This idea sits outside of the TypeScript language design constraints Suggestion An idea for TypeScript

Comments

@niemyjski
Copy link

This would resolve a problem when you have tsconfig.json files in a folder. It would be cool if you could select the configuration (Think Debug or Release). By default it would just be the default configuration.

That's why I think it would be nice to support a naming convention where you have:

  • \tsconfig-es5.json
  • \tsconfig-es6.json

and then you could apply those rules under the specific target (es5 or es6)..

Reference #2868 (comment)

@mhegazy
Copy link
Contributor

mhegazy commented Apr 22, 2015

There is a large number of possible combinations of options that would be hard to satisfy them all in names, e.g. tsconfig-es5-commonjs-noImplicitAny.json, i would expect instead you would have tsconfig-debug.json or debug\tsconfig.json and your build system will check the debug/release flags to know which one to build.

I believe #2869 would make this even easier by allowing you to specify a full path to a json file.

@mhegazy mhegazy added Suggestion An idea for TypeScript Out of Scope This idea sits outside of the TypeScript language design constraints labels Apr 22, 2015
@mhegazy mhegazy closed this as completed Apr 22, 2015
@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Out of Scope This idea sits outside of the TypeScript language design constraints Suggestion An idea for TypeScript
Projects
None yet
Development

No branches or pull requests

2 participants