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

Wrong configuration is being used #90

Open
alexlafroscia opened this issue Jul 11, 2016 · 9 comments
Open

Wrong configuration is being used #90

alexlafroscia opened this issue Jul 11, 2016 · 9 comments

Comments

@alexlafroscia
Copy link
Collaborator

alexlafroscia commented Jul 11, 2016

Somehow, I'm seeing some configuration options applied during testing that shouldn't be applied.

I have a bunch of tests failing due to the comma-dangle rule being applied.

not ok 8 PhantomJS 2.1 - ESLint - acceptance/_checkout-test.js should pass ESLint
    ---
        message: >
            acceptance/_checkout-test.js should pass ESLint.
            162:34  - Unexpected trailing comma. (comma-dangle)
            230:36  - Unexpected trailing comma. (comma-dangle)
        Log: |
    ...

However, as far as I can tell from the command line, that rule is "off".

$ eslint --print-config app | grep comma
    "comma-dangle": "off",
    "comma-spacing": "off",
    "comma-style": "off",

$ eslint --print-config tests | grep comma
    "comma-dangle": "off",
    "comma-spacing": "off",
    "comma-style": "off",

If I run eslint from the command line none of the files fail, nor to they fail from ESLint being run through my editor. That property must be turned on from somewhere, but I just can't tell where.

@Turbo87
Copy link
Member

Turbo87 commented Jul 12, 2016

eslint:recommended includes that rule, which is used by the default config in this project. maybe your local eslint isn't picking up that config?

@alexlafroscia
Copy link
Collaborator Author

Yeah, maybe that's what it is. I wonder if eslint outside of Broccoli has issues with the relative path to the configuration that comes with ember-cli-eslint?

@cafreeman
Copy link

cafreeman commented Jul 29, 2016

FWIW, this seems to still be an issue. I even went so far as to copy/paste the same config in to both the test and app config files and I still see discrepancies between the two.

eslint --print-config app and eslint --print-config tests even return the exact same results :(

@alexlafroscia
Copy link
Collaborator Author

Weird, I figured it was something going wrong on my machine. That seems to happy a lot since I often have packages npm linked which causes all kinds of problems.

@bartocc
Copy link

bartocc commented Aug 10, 2016

Having the issue too

@alexlafroscia
Copy link
Collaborator Author

@cafreeman @bartocc do you both have

require.resolve('ember-cli-eslint/coding-standard/ember-application')

in your config to load the default settings? Or a relative path to the configuration in the node_modules directory?

@bartocc
Copy link

bartocc commented Aug 12, 2016

@alexlafroscia , yes, I have this line.

2 days ago, I had to add 'comma-dangle': 0 to my rules to make my files ESLint compliant.
I just tried to remove 'comma-dangle': 0 and now no more errors ...

I'll update this conversation if the error comes back

@bartocc
Copy link

bartocc commented Aug 12, 2016

actually, I still get the error, but only when running tests on /tests. eslint /path/to/my/file.js does not complain

@alexlafroscia alexlafroscia reopened this Aug 12, 2016
@alexlafroscia
Copy link
Collaborator Author

Clearly this is still an issue so I'm going to open this again. It might be an upstream problem in broccoli-lint-eslint though, since ember-cli-eslint really just wraps that package.

Turbo87 pushed a commit that referenced this issue Oct 15, 2018
Bumps [ember-cli-dependency-checker](https://github.com/quaertym/ember-cli-dependency-checker) from 2.0.1 to 3.0.0.
<details>
<summary>Commits</summary>

- [`b41dc34`](quaertym/ember-cli-dependency-checker@b41dc34) 3.0.0
- [`8b6378a`](quaertym/ember-cli-dependency-checker@8b6378a) Merge pull request [#91](https://github-redirect.dependabot.com/quaertym/ember-cli-dependency-checker/issues/91) from jacobq/update-ember-cli
- [`680dc7d`](quaertym/ember-cli-dependency-checker@680dc7d) v2.2.1
- [`614de60`](quaertym/ember-cli-dependency-checker@614de60) Upgrade dependencies to latest major version
- [`9947062`](quaertym/ember-cli-dependency-checker@9947062) Replace 'var' with 'let'/'const'
- [`7f22624`](quaertym/ember-cli-dependency-checker@7f22624) ember-cli-update (--to 3.2); drop node v4.x
- [`bfe155d`](quaertym/ember-cli-dependency-checker@bfe155d) Merge pull request [#90](https://github-redirect.dependabot.com/quaertym/ember-cli-dependency-checker/issues/90) from jacobq/gh-issue-89
- [`1ca3d53`](quaertym/ember-cli-dependency-checker@1ca3d53) Accept equivalent tar ball paths
- [`58d18ac`](quaertym/ember-cli-dependency-checker@58d18ac) 2.2.0
- [`90b33ac`](quaertym/ember-cli-dependency-checker@90b33ac) Merge pull request [#88](https://github-redirect.dependabot.com/quaertym/ember-cli-dependency-checker/issues/88) from tschoartschi/master
- Additional commits viewable in [compare view](quaertym/ember-cli-dependency-checker@v2.0.1...v3.0.0)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=ember-cli-dependency-checker&package-manager=npm_and_yarn&previous-version=2.0.1&new-version=3.0.0)](https://dependabot.com/compatibility-score.html?dependency-name=ember-cli-dependency-checker&package-manager=npm_and_yarn&previous-version=2.0.1&new-version=3.0.0)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

Dependabot will **not** automatically merge this PR because it includes a major update to a development dependency.

---

**Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com).

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>
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

No branches or pull requests

4 participants