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

Remove the "Disable linting" checkbox #1140

Merged
merged 2 commits into from
Nov 2, 2023

Conversation

nelstrom
Copy link
Contributor

Addresses #1139.

This PR does two things:

  1. It removes the "Disable linting" checkbox
  2. It removes references to the nolint query param from the implementation

Removing the checkbox is my main goal with this PR, whereas removing references to nolint is just me being thorough. It's possible that we want to keep the nolint handling in place for the sake of backwards compatibility, in which case I'm happy to revert the second change.

Before:

qunit-nolint-before

After:

qunit-nolint-after

@nelstrom
Copy link
Contributor Author

As an afterthought: maybe it's worth including some documentation instructing how to add the "Disable linting" checkbox back, for anyone who still uses this feature?

@NullVoxPopuli
Copy link
Sponsor Collaborator

NullVoxPopuli commented Sep 26, 2023

Before determining if this is a fix or breaking change, is there a way you can check if ember-cli-template-lint or ember-cli-eslint:

  • work within the supported
    • ember-cli range: ember-cli ~v4.8.1, ~v4.12.2, >= v5.1
    • ember-auto-import@v2
    • node 16+
  • introduce their own "Disable linting" flag
  • what happens if locally, ember-qunit doesn't have Disable linting, and someone wants to disable linting and happens to have one of the ember-cli*lint packages installed?

Thank you!!!!

If the answer to the first is "no", or if the answer to the second is "yes", then we don't need to worry about compat.

@nelstrom
Copy link
Contributor Author

@NullVoxPopuli to investigate that, would it be a question of doing the following:

  1. Using ember-cli version 4.8.1, run ember new to create a new app
  2. In the new app, install ember-cli-eslint
  3. Make the new app use Node v16 and ember-auto-import@v2
  4. Check that the new app runs ok

If that all works, then I could replace the ember-qunit dependency with the version in this branch, and see if it causes anything to break.

Does that sound like a plan? Or did I misunderstand you?

@nelstrom
Copy link
Contributor Author

Taking a closer look at the package.json file in ember-cli-eslint, a few things jump out at me:

  1. "node": "6.* || 8.* || >= 10.*"
  2. "ember-cli": "~3.9.0",
  3. "ember-cli-qunit": "^4.3.2", - it doesn't depend on ember-qunit, but instead depends on ember-cli-qunit (also deprecated)
  4. No mention of ember-auto-import

This is an addon from the pre-Octane era of Ember. It's going to be difficult to get ember-cli-eslint working with any of the current LTS releases of Ember/EmberCLI.

@NullVoxPopuli
Copy link
Sponsor Collaborator

True, so, because ef that ember-cli range, it's not something we need to worry about. Excellent! Thanks for looking!

@NullVoxPopuli NullVoxPopuli merged commit bccde94 into emberjs:main Nov 2, 2023
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants