# Allow both integer and string request IDs in LSP \(\#7662\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/f01763a1fa7a0277293024fa37e93c9c0e0801a3)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: f01763a1fa7a0277293024fa37e93c9c0e0801a3

Requested commit: f01763a1fa7a0277293024fa37e93c9c0e0801a3

Commit: f01763a1fa7a0277293024fa37e93c9c0e0801a3

Tree: 59cc75a852b804797397e7083004182d778d308f

Author: Michal Příhoda

Committer: GitHub

## Message

```
Allow both integer and string request IDs in LSP (#7662)

Zed's LSP support expects request messages to have integer ID, Metals
LSP uses string. According to specification, both is acceptable:

interface RequestMessage extends Message {

	/**
	 * The request id.
	 */
	id: integer | string;

...
This pull requests modifies the types and serialization/deserialization
so that string IDs are accepted.

Release Notes:

- Make Zed LSP request ids compliant to the LSP specification
```

## Parents

- [2dffc5f6e1526a4494f34bfaca8c738998712d6b](https://git.cafe/gitcafe/zed/commit/2dffc5f6e1526a4494f34bfaca8c738998712d6b?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/f01763a1fa7a0277293024fa37e93c9c0e0801a3?format=markdown)