Skip to content

formatCodeOptions are ignored in JS Output #196

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

Closed
sclausen opened this issue Mar 19, 2015 · 5 comments
Closed

formatCodeOptions are ignored in JS Output #196

sclausen opened this issue Mar 19, 2015 · 5 comments

Comments

@sclausen
Copy link

It seems that formatCodeOptions in tsconfig.json are simply ignored.
setting intent size, tabsize or newlinechar doesn't affect the output.

Without compilerOptions, files and so on, my tsconfig.json looks as follows

{
  "formatCodeOptions": {
    "IndentSize": 2,
    "TabSize": 2,
    "newLineCharacter": "\n"
  }
}
@basarat
Copy link
Member

basarat commented Mar 19, 2015

doesn't affect the output.

Just to clarify: do you mean JS output or formatting commands output

@sclausen
Copy link
Author

Yes, exactly. Sorry I didn't pointed this out.

@basarat
Copy link
Member

basarat commented Mar 20, 2015

Yes, exactly. Sorry I didn't pointed this out.

Again: do you mean JS output or formatting commands output ❤️

@sclausen
Copy link
Author

Oh damn that was an either-or question. I'm so sorry!
I meant the js output.

@basarat
Copy link
Member

basarat commented Mar 20, 2015

Cool. Its not designed to impact the JS output. Its designed for format TypeScript. I've updated the docs to clarify. There is no plan to control JS output formatting at the moment. Perhaps take it up with https://github.com/Microsoft/TypeScript 🌹

@basarat basarat changed the title formatCodeOptions are ignored formatCodeOptions are ignored in JS Output Mar 20, 2015
@TypeStrong TypeStrong locked and limited conversation to collaborators Jan 20, 2019
angelestelar5z added a commit to angelestelar5z/atom-typescript that referenced this issue Aug 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants