Collections are not propogated to run/test/debug tasks.

[Oikio]

Good day,

Adding collections to OLS to get indexing and autoimport works, including goto definitions. But run/test/debug tasks provided by extension do not work because Odin executable expects -collection:project=. to be passed.

Example OLS config:

{
  "$schema": "https://raw.githubusercontent.com/DanielGavin/ols/master/misc/ols.schema.json",
  "collections": [{ "name": "project", "path": "." }]
}

---

I am new to Odin ecosystem and not sure if it's intended or a bug, but using collection seems like a default way to go with OLS according to documentaion and by doing so user has to recreate all tasks and debug configurations themself.

[rxptr]

Hey, thanks for the report,

Collections in ols.json are only intended for OLS to know how to resolve those imports for the language server; the odin compiler itself has no config file, it only learns about a collection from a -collection:name=path flag on the command line. This extension's run:/test:/build:/check: tasks are static JSON that Zed executes directly, and Zed's extension API doesn't currently give extensions a hook to read project config and inject extra arguments into a task before it runs. So this isn't something the extension can fix on its own; doing tricks to resolve the path has been done before, but is flaky for different OS and setups, so it would need a new capability from Zed's extension API to be possible.

I will update the README for further info and workaround.

[Oikio]

Makes sense, thank you for the quick response and explanation. Having tasks.json and debugger.json examples to copy-paste and/or explanation would be very useful for users.