-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
Plan v12 Release #1535
Comments
there is also
|
Yup! Thank you! |
@patricklx if #1939 should be enabled as a recommended rule, can you open a PR to do that? Any other changes to complete? I'm thinking we should release an alpha version with all these changes so people can test them out, given the revert that happened in the last release. CC: @NullVoxPopuli |
i think it should! |
@patricklx can you open PRs for:
Then I think we're ready for an alpha release. |
For the typescript dependencies I will look into it on Monday |
Sounds good. Here is the first alpha version. Please help test it: https://github.com/ember-cli/eslint-plugin-ember/releases/tag/v12.0.0-alpha.0 |
Second alpha version, please test: https://github.com/ember-cli/eslint-plugin-ember/releases/tag/v12.0.0-alpha.1 |
@NullVoxPopuli @patricklx how close do you think we are to releasing v12.0.0? Are any more breaking changes still needed? Is gjs/gts fairly stable? It doesn't have to be perfect since bug fixes can continue after the release, but should be in good shape. |
Should be the last thing, iirc. |
Shall I release v12 final in the next few weeks? Has testing of the alpha gone well? |
Atm, I need to see what's going on with this repo: NullVoxPopuli/limber#1604 |
Looks like a potential bug in the template-no-let-reference rule |
We're making progress with the parser -- few more issues: |
With these last PRs remainaing, my test repo is fully green:
Once those are merged, I'll want to test on probably two other repos for confidence. |
Here is the other test repo: universal-ember/ember-primitives#209 Found an issue with SVG elements not being "defined" |
I have 3 repos using the alpha:
All have "green" lints.
So this last upgrade PR should be all we need: #2055 to release v12. I could always do more testing, but making sure the parser is working on lots of varying code was my main concern. Any other testing, I feel, would be rules / configuration based -- and I haven't run in to any issues with that yet -- but at the same time, I need to re-do all my ESLint configs across all my projects to do the ESLint 9 flat config thing. But that should just be a me thing and not an eslint-plugin-ember thing. |
I'll release the final version in the next several days. |
We are waiting until we have enough breaking changes before proceeding with this release.
If there isn't much urgency with any specific breaking changes, then we normally just wait until we can drop Node versions before a release. If there are changes that we need/want to get out sooner, we can consider an earlier release. Please comment if a major release would be helpful.
Planned changes:
recommended
rules:recommended
rules:no-at-ember-render-modifiers
,no-deprecated-router-transition-methods
,no-implicit-injections
,no-runloop
,no-tracked-properties-from-args
, #1963recommended
rule:template-no-let-reference
#1977useAt
option default totrue
at inno-get
rule #1965ecmaVersion
to2022
#1978@typescript-eslint/
dependencies to v6 #1984Releases:
The text was updated successfully, but these errors were encountered: