-
Notifications
You must be signed in to change notification settings - Fork 433
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
Lombok support v1 #2519
Lombok support v1 #2519
Conversation
7960637
to
63c6947
Compare
Pls fix tslint errors first. You can run the command |
63c6947
to
44648ef
Compare
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.
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. Tried it on maven and gradle lombok project, it works well. I think it's ready to merge.
In the current version, it prompts the user to reload the window for lombok support. We have tried restarting the language server without reloading, which is technically possible, but we found that this has side effects on third-party extensions, some of which report errors about delegate command exists. So in v1, we still use reloading to restart the language server. We will further investigate how to make third-party extensions work properly with language server restart.
Once the PR is merged, we'll update the wiki description as well. https://github.com/redhat-developer/vscode-java/wiki/Lombok-support
1. It can automatically detect whether the project has imported the lombok by checking all classpath. 2. It can show the current version of the lombok in the language status bar. 3. It can dynamically detect the version change of the lombok. Signed-off-by: Yuhao Xiao <t-yuhaoxiao@microsoft.com>
Signed-off-by: Yuhao Xiao <t-yuhaoxiao@microsoft.com>
Signed-off-by: Yuhao Xiao <t-yuhaoxiao@microsoft.com>
README.md. 2. Update the tooltip of the LombokConfigureCommand. 3. Remove the unnecessary updateActiveLombokPath at initialization. Signed-off-by: Yuhao Xiao <t-yuhaoxiao@microsoft.com>
- Use lockFileVersion v1 for now as v2 would require moving to Node 16 in our builds Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
aeee7d2
to
3cfbd9d
Compare
I've rebased this change and just reverted the part about using lockFileVersion 2 since that would require npm v7, and we currently build with Node v14 (npm v6). The addition of htmlparser2 seems to work just fine keeping the lockfile version the same. |
Add the lombok support: