Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 20 2018 03:40
    666don commented #2289
  • Aug 11 2017 16:16
    coveralls commented #1895
  • Jul 20 2017 14:45
    cashburn commented #2268
  • Jul 20 2017 14:45
    cashburn commented #2268
  • Jun 15 2017 11:14

    markelog on master

    Tests: handle error messages wi… (compare)

  • Apr 28 2017 14:00
    dasdany closed #2295
  • Apr 28 2017 14:00
    dasdany commented #2295
  • Apr 28 2017 14:00
    dasdany closed #2294
  • Apr 28 2017 14:00
    dasdany commented #2294
  • Apr 28 2017 13:59
    dasdany commented #2294
  • Apr 28 2017 13:57
    dasdany opened #2295
  • Apr 28 2017 13:33
    bboydflo commented #2294
  • Apr 28 2017 08:39
    dasdany opened #2294
  • Mar 17 2017 01:42
    coveralls commented #1500
  • Dec 19 2016 16:38
    KeithPepin-MW commented #1501
  • Dec 19 2016 16:38
    KeithPepin-MW commented #1501
  • Dec 19 2016 16:38
    KeithPepin-MW commented #1501
  • Dec 19 2016 16:37
    KeithPepin-MW commented #1501
  • Dec 19 2016 16:17
    KeithPepin-MW commented #1501
  • Dec 19 2016 16:15
    KeithPepin-MW commented #1501
Johan Vaage
@Jovaage
I'm using to jscs to automatically fix my js files.
But I can't get the requireUseStrict rule to fix them.
It reports the error, but it doesn't fix it.
I'm also enforcing requireLineFeedAtFileEnd and requirePaddingNewLinesAfterUseStrict, and they do work.
Oleg Gaidarenko
@markelog
Some rules are autofixable and some are not
Johan Vaage
@Jovaage
Is that specified anywhere?
Oleg Gaidarenko
@markelog
nope
Johan Vaage
@Jovaage
Is that rule not supported yet?
When just installing jscs, it reports fine, but when using the plugin in WebStorm, and using gulp-jscs, it complains that the rule isn't supported.
Oleg Gaidarenko
@markelog
That's probably because
Oleg Gaidarenko
@markelog
local version of jscs is old
so i would recomended to reinstall jscs
current one is 3.0.3
Charlie Robbins
@indexzero
@markelog everything OK with jscs? I just saw the 100+ issues get closed with "At this point only major and CST related bugs will be fixed.”
Oleg Gaidarenko
@markelog
Haven’t you heard? We are merging with eslint - https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2
so support is very limited at this point
Charlie Robbins
@indexzero
Nope! This makes way more sense now
I guess this got burried in my Twitter feed or something.
Charlie Robbins
@indexzero
Well best of luck with everything! Can’t wait to hear more about the cst integration in eslint
Oleg Gaidarenko
@markelog
that’s a big “if” at the moment - cst impl in eslint
thank you though, for all your support :)
Charlie Robbins
@indexzero
@markelog well I think one of the things I’m going to do with this information now is compile an issue that has all the jscs rules with autofix and the eslint equivalents in the hopes we get to 1-1 down the road
Oleg Gaidarenko
@markelog
yeah, that’s plan
Alexej Yaroshevich
@zxqfox
There is polyjuice package that helps)
Oleg Gaidarenko
@markelog
yeah, it has couple issues though, works weird sometimes
Charlie Robbins
@indexzero
Yeah, I have a thing I used to run both. https://github.com/indexzero/fashion-show
But now we will just run eslint directly
Oleg Gaidarenko
@markelog
many people do, this is why we come up with this solution :)
cool idea with fashion-show though, like standard or xo on rails
Kishore varma
@kishorevarma
Hi
Kishore varma
@kishorevarma
I am getting Expected token value ":" but = found when I use class in my file
I am using latest jscs-dev/node-jscs version
can anybody help me please
Kishore varma
@kishorevarma
I found the issue its because of using default values in de-structuring like { foo = 23 , bar} = {bar: 20}
Alexej Yaroshevich
@zxqfox
Do you get it in 3.0?
Eran Yanay
@eranyanay
Hi everyone. I see dev-jscs is deprecated. Does it means the Plugin API is deprecated as well? I would like to extend my jscs checks with a custom rule of my own, but didnt find many articles about it.
Thomas Grainger
@graingert
I've got a mix of legacy '.js' files and modern '.es2015.js' files
and I only want to lint the modern files
how can I do this?
@eranyanay yeah basically. It's best to add it to eslint if you can
jscs-dev/node-jscs#2273
Eran Yanay
@eranyanay
When looking at the rules and trying to write my own, I see stuff like iterateNodesByType, and I wish to know the available types. Where is it listed?
Jonathan Neal
@jonathantneal
The teams have merged, but has the code base? What's the current thinking?
Henry Zhu
@hzoo
@jonathantneal no direct codebase merging
basically moving to eslint and finding places to combine ideas
whereever jscs is doing better we can make an issue for it
Thomas Grainger
@graingert
@markelog any chance of re-opening jscs-dev/node-jscs#2273 ?
it's definitely a bug, because I've got a fix for it.
Andrea Sonny
@andreasonny83
hello
sorry about the stupid question. Do you how a best practice for indenting multilines in JavaScript? I’m still looking for a standard when I write JS code and I have a jscs limitation to 80 chars per line
Thomas Grainger
@graingert
@markelog looks like cst/cst#118 wasn't fixed in cst/cst#125 see: cst/cst#126
Thomas Grainger
@graingert
@markelog sorry I don't have access to a machine with node setup on it.