Add support for URI fragments

[Lysxia]

This is useful because in VSCode, file system URIs can contain line numbers in the fragment: file:///path#N.

[voodoos]

Do you have examples of requests to the server that require correct handling of these fragments ? Or is it that you use the lsp library in another application ?

[Lysxia]

I am using lsp in my own language server where I would like to send a URI with a fragment to the client. Specifically, I'm trying to use the DocumentLink feature to link to another file. The target of DocumentLink can only be a URI, with no field for position information. The fragment lets a URI point to a file location.

[rgrinberg]

Thanks for the contribution. I think you forgot to promote the test. Can you review them at 73363fd (#1387)

If those look correct to you, this PR is good to go.

[Lysxia]

The tests look good to me!

[rgrinberg]

LGTM. Bear in mind that the LSP library offers no API stability.

[coveralls]

Pull Request Test Coverage Report for Build 4589

Details

• 3 of 4 (75.0%) changed or added relevant lines in 1 file are covered.
• 17 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.007%) to 21.913%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
lsp/src/uri0.ml	3	4	75.0%

Files with Coverage Reduction	New Missed Lines	%
ocaml-lsp-server/src/import.ml	1	34.69%
lsp/src/uri_lexer.ml	16	79.76%

Totals
Change from base Build 4580:	0.007%
Covered Lines:	5562
Relevant Lines:	25382

---

💛 - Coveralls