-
Notifications
You must be signed in to change notification settings - Fork 19
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
Update eslint
to v9
#5
Comments
+ Evaluating results. Please wait... |
|
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 17.8 |
Issue | Task | 1 | 25 |
Review | Comment | 1 | 32.6 |
Review | Comment | 1 | 16.3 |
Conversation Incentives
Comment | Formatting | Relevance | Reward |
---|---|---|---|
We are using an old version of `eslint` which differs in... | 17.8code: count: 3 score: "3" words: 4 | 1 | 17.8 |
## What changed - pinned package versions to avoid (bad) surpri... | 32.6h2: count: 1 score: "2" words: 2 li: count: 7 score: "14" words: 73 code: count: 1 score: "2" words: 1 | 0.66 | 32.6 |
## What changed - pinned package versions to avoid (bad) surpri... | 16.3h2: count: 1 score: "1" words: 2 li: count: 7 score: "7" words: 73 code: count: 1 score: "1" words: 1 | 0.66 | 16.3 |
I guess the rewards calculation for the pull comments are very broken this time @gentlementlegen When v2? |
@0x4007 Seems v2 went on a break as well, I do not see anymore logs. Might be because it's not using the main branch for deployments (I think I sent you a message about this). Waiting of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are using an old version of
eslint
which differs in the way of how the configuration is defined. A new format calledflat format
is now in used, and has benefits like having a fully type supportedtypescript
check within the configuration. It would be nice to benefit from that upgrade for the new plugins.References:
https://eslint.org/docs/latest/use/migrate-to-9.0.0
https://typescript-eslint.io/getting-started
The text was updated successfully, but these errors were encountered: