Hi,
The code docs I’m editing are accessed via an extension (InterSystem ObjectScript) that uses the FileSystemProvider API to serve them. Unfortunately, Cody does not seem to “see” them, as I get messages like “Please select text before running…” even though I have selected it. Works fine for a copy of the same code held in local files.
Is there anything I can do to make this work, please? If not, are there any plans to enhance Cody to see these files.
Thanks,
Mike
Hey @mikeAtDedalus
Cody can only recognize files that are directly in the repository. So files outside the repository won’t be fetched as context. The InterSystem ObjectScript extension does not seem to put the documents in the repository, but in its own local storage. You can ask the extension owner for a feature that lets you store the documents locally.
Thanks for the quick reply.
The documents are directly available inside VS Code - the FileSystemProvider API is a standard part of VS Code (I’m told) - but yes, they are not in a Git repo or directly available on the local file system. They work a bit like stored procedures in a SQL database, so are not normal “files” at any point, just pulled in for edit, so I assume that’s the issue. I’ll contact the owner about copying to ordinary files, but it’s not really a solution as storage and compile need to happen inside the database.
I’m surprised Cody can’t at least see the contents of the current edit window or retrieve currently selected text. Surely it doesn’t pull data from a file system for those? Maybe InterSystems have not configured FileSystemProvider correctly to allow for other extensions to request document info. I’ll ask.
Mike
I’ve installed Amazon Q, and it has no problem seeing the files I’m editing, and the current selection, even though it’s via the FileSystemProvider API. So I think the problem is in Cody. It’s a shame, Cody is a lot better than Q.