-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Integrate eslint with eslint-config-standard #385
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job!
Btw, you can use the |
I implemented the review comments and rebased the branch. Now, the build will fail because |
I have now enabled eslint globally for all packages and thanks for mentioning |
Build is green. Everything is in. If you agree with the latest changes this is good to go, I think. |
Make disposable.ts in both packages identical for now
I will produce new |
Sounds good! What will we wait for before releasing a final version? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Actually a good question. We don't really have official beta tester. And a major version change should not immediately cripple correctly configured projects depending on here. |
It seems pretty safe to release a major version to me, and release fixes later, or we won't get any feedback I'm already testing the new vscode-api approach for more than a week, and everything else is just refactors, it can't break things, can it? |
Let's go |
We should archive the repos of |
Will do it on my side |
done! |
✅ |
I have based this branch on your branch, because otherwise the changes are obsolete again soon and would need to be redone. Therefore the target branch is currently also
use-monaco-vscode-api
@CGNonofr I used
eslint-config-standard
, but I made some adjustments:no-dupe-class-member
is offno-redeclare
,no-useless-constructor
andno-void
have been reduced to warn (you should check if the code should or could be changed or ifeslint-disable
should be set instead and we can then remove the rule reduction)This closes #366