Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Karolis Narkevicius
    @KidkArolis
    they even created a separate standardx where that's the only difference
    why does it make sense for them to now allow it (or maybe it doesn't)
    and makes sense here to allow it
    because.. you can just eject..
    Adam Stankiewicz
    @sheerun
    I think it's needed even just to disable some rules you don't need in your project. For example in mine I do:
    "react/prop-types": "off",
    "no-eval": "off"
    Becase at some point I need to use eval and we decided to not use react prop types
    Karolis Narkevicius
    @KidkArolis
    I think those are off already in standard, actually
    that's the nice thing about standard, in many years of using it, I never needed to disable any rule..
    or ok, I do sometimes, inline, you know // eslint-disable no-eval
    or whatever the syntax is
    was always good enough
    I mean, I just wanna make sure we open this up for a good reason, I guess..
    Adam Stankiewicz
    @sheerun
    There are also other things, like definig globals or using custom plugins and configs
    e.g. we use "globals": {
    "drift": true,
    "localStorage": true
    },
    because we use drfit plugin that installs as global variable
    and localStorage that was not supported by some version of standard
    Karolis Narkevicius
    @KidkArolis
    you can do globals in package.json#healthier.globals, like with standard..
    Adam Stankiewicz
    @sheerun
    You can configure eslint with eslintConfig in package.json as well. I think it would be reasonable to keep all configuration options instead of creating new one
    Karolis Narkevicius
    @KidkArolis
    but then this is deviating from standard, part of the appeal is the familiarity with that tool
    for example, I'm very used to setting up standard globals, ignores, parser
    so to me it's part of the selling point.. but hmmm
    Adam Stankiewicz
    @sheerun
    tbh it's mostly about ability to override some of healtheir config, not about using .eslintrc
    so if you allow to override it with package.json#healther it's ok
    but for example I would like to add extra extend to set of linting rules
    For example how would you add to your project https://github.com/mochajs/eslint-config-mocha ?
    Karolis Narkevicius
    @KidkArolis
    but don't you think that not having extensibility was kind of part of standard's success/appeal? just wondering :)
    Adam Stankiewicz
    @sheerun
    They already have readme that says "add something to .eslintrc"
    It is, but it's also why I'm not using standard itself :)
    Karolis Narkevicius
    @KidkArolis

    this eslint-config-mocha doesn't seem to be doing much?

    https://github.com/mochajs/eslint-config-mocha/blob/master/.eslintrc.json

    Adam Stankiewicz
    @sheerun
    I don't think it's good in long run
    It was just an example :)
    Karolis Narkevicius
    @KidkArolis
    I mean, I know this was just an example, but it's part of why people should like .. not worry about this stuff too much
    if it's really good, then it would get rolled into eslint-config-standard
    like promise, node, react was..
    but maybe there are things like eslint-config-vue and such
    Adam Stankiewicz
    @sheerun
    I think you need to think what to do for example with eslint-config-vue or eslint-config-react
    Karolis Narkevicius
    @KidkArolis
    yeah, I never used eslint-config-react, just because standard doesn't seem to support it, I always wondered how people us it..
    Adam Stankiewicz
    @sheerun
    I use eslint with config standard + these
    eslint-config-standard has 5x more daily downloads than standard
    Karolis Narkevicius
    @KidkArolis
    interesting!
    Adam Stankiewicz
    @sheerun
    From my experience standard is quickly not enough for linting and people "eject" to eslint
    We had nice chat but, I need to go for today :)
    Karolis Narkevicius
    @KidkArolis
    I/we always just stuck with just standard
    all right, thanks so much for the feedback!
    Adam Stankiewicz
    @sheerun
    We can talk tomorrow if you want
    bye
    Karolis Narkevicius
    @KidkArolis
    I'm pretty much inline with all of it
    see ya, take care
    Karolis Narkevicius
    @KidkArolis
    @sheerun are you around?