URI conflicts with Codeium, an AI tool, for autocompleting ObjectScript code

[RyszardWithAZ]

When using the Intersys Server Manager to open namespaces and do server-side editing of code, the server manager updates the workspace file to have the namespace in the uri as if it were a port: "uri": "isfs://machine:user"

Unfortunately, our AI VSCode plug-in, Codeium, is interpreting that as a port and therefore it crashes.

If instead we don't use the server manager and manually create our uris that look like this: "uri": "isfs://machine?ns=user", then it works.

Is there a way of fixing the server manager to do it this way as well? Half of our engineers have their VSCode set up one way, and half the other way. It would be good if they could ALL work with our UI plug-in no matter which setup they used.

[isc-bsaviano]

@RyszardWithAZ Can you share what those errors look like? IMO this is a bug in Codeium. The spec for the VS Code URI implementation does not state that the authority part has to be interpreted as a host with an optional port.

Sources:
https://code.visualstudio.com/api/references/vscode-api#Uri
https://github.com/microsoft/vscode-uri?tab=readme-ov-file#vscode-uri

[RyszardWithAZ]

Here's an example of the errors.

[isc-bsaviano]

Thanks for that. What's the behavior when the namespace is in the query string? I don't use that tool so I'm not sure what it does or how it gets the text of the files. If it uses the VS Code API to get the file text then it shouldn't have any problems with our URIs.

[RyszardWithAZ]

I don't know how it works, but when it works, Codeium performs ObjectScript autocompletion within routines or classes, with a full AI behind it. So I could write comments about what a method could do and it could suggest at least half the code for the method, for example. Or when writing code, it will autocomplete a for loop or whatever. But somehow it's relying on the file uris to process, and it's reading the :namespace as a port.

[isc-bsaviano]

@RyszardWithAZ Is there a way for you to report issues to whoever develops that tool? It looks like whatever library it's using to implement the Language Server Protocol isn't parsing URIs according to the spec. The LSP uses the same URI spec as VS Code.