Skip to content

Conversation

@simark
Copy link
Contributor

@simark simark commented Jul 18, 2018

I enabled a few more rules. They were mostly fixed tslint's --fix.

Some of them are about formatting. I don't mind what the formatting rules are, but I think it helps if they are enforced by the linter, so you don't loose time later arguing/commenting about spaces/semicolons/etc.

simark added 10 commits July 18, 2018 10:52
Rationale from the rule's page:

AMD-style require([]) and CommonJS-style require("") statements are
environment-specific and more difficult to statically analyze.

ES2015-style imports are part of the JavaScript language specfication
and recommended as the path going forward. TypeScript will compile them
to environment-specific forms as needed.
This is not a big deal, but I think it makes the code a bit nicer.
The project seems to use tabs, so we can enable the tslint rule for it.
Not really necessary, but it's nice if code is consistently formatted.
I'm not sure what is your preference here, but I've seen both styles:

  } else {

and

  {
  else {

I think it would be nice to have a consistent style, and the former is
more common.
@WebFreak001
Copy link
Owner

hm ok cool, didn't think there were so many missing semicolons. Definitely good to have it all consistent now though.

@WebFreak001 WebFreak001 merged commit 606a25b into WebFreak001:master Jul 18, 2018
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.

2 participants