fix(lsp): FlyCheck request params

[fengys1996]

Hi, I encountered a problem and try to solve it.

When I manually trigger a flyCheck via :RustLsp flyCheck, the rust analyzer does not perform the corresponding flyCheck.

The minimal configuration of rust analyzer as follows.

["rust-analyzer"] = {
	check = {
		command = "check",
		workspace = false,
	},
}

Looked through the code of the rust analyzer and found that the serialization of the flycheck_params is problematic. The related code see here.

And this PR fixes the serialization problem of flycheck_params.

[github-actions]

Review Checklist

Does this PR follow the Contribution Guidelines? Following is a partial checklist:

Proper conventional commit scoping:

• For example, fix(lsp): some lsp-related bugfix

• Pull request title has the appropriate conventional commit prefix.

If applicable:

• Tested
  • Tests have been added.
  • Tested manually (Steps to reproduce in PR description).
• Updated documentation.

[mrcjkb]

Thanks 🙏

This used to work. I wonder if something changed in the nvim function or in rust-analyzer's deserialization that broke this 🤔

[fengys1996]

Thanks 🙏

This used to work. I wonder if something changed in the nvim function or in rust-analyzer's deserialization that broke this 🤔

If worksapce=false is set, flyCheck will execute cargo check -p package, and package is determined based on the passed uri. If serialization fails, flyCheck does nothing, since the passed uri is none.

If worksapce=true is set (default true), flyCheck executes cargo check --workspace, and the success or failure of fly check params serialization does not affect the execution of flyCheck.

😃

[mrcjkb]

Ah, thanks for the clarification 🙏
Makes sense.