-
Notifications
You must be signed in to change notification settings - Fork 0
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
refactor(lsp): remove useless logging & methods #16
Conversation
let _init_params: InitializeParams = serde_json::from_value(init_params).unwrap(); | ||
|
||
for msg in &connection.receiver { | ||
// TODO: Handle trace levels and notifications instead of just printing them to stderr. | ||
eprintln!("new msg: {:?}", msg); |
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.
This log is unnecessary, you can set weblsp.trace.server
to either messages
or verbose
for the client to output what messages you received / sent
// Handle the rest of the messages. | ||
match msg { | ||
Message::Request(req) => { | ||
let request = | ||
requests::handle_request(req, &mut css_language_service, &connection)?; | ||
match connection.handle_shutdown(&req) { |
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.
didn't know this existed when I made the initial shutdown support, turns out this does the same as what I did manually. We still need a global state eventually
CodSpeed Performance ReportMerging #16 will improve performances by ×2.2Comparing Summary
Benchmarks breakdown
|
What does this change?
Just some small changes, using existing methods instead of new ones, renamed settings etc.
How is it tested?
N/A
How is it documented?
N/A