feat: Procedural Macro Resolution Doesn't Work for Nested Cairo Projects

[machuwey]

Related issue: #18 #20
@0xpantera

Currently, procedural resolution macros work perfectly if the opened cairo project is at the repository root. However, if Cairo contracts are nested deeper within a monorepo structure (such as under an apps folder), the procedural macro resolution does not function properly.

Example monorepo layout:

├── apps
│   ├── contracts
│   ├── frontend
│   └── indexer

In this scenario, the procedural macros are not resolved correctly.

Would it be possible to support procedural macro resolution for Cairo projects that are not directly located in the root directory, but nested deeper in a folder structure?

[0xpantera]

In the example layout is the Scarb.toml file inside apps/contracts/? I think it's possible. Will take a look.

[0xpantera]

There's an upstream issue in CairoLS. I'll try a workaround but in the meantime you could try opening Zed in the Cairo folder instead of the monorepo root.

[machuwey]

In the example layout is the Scarb.toml file inside apps/contracts/? I think it's possible. Will take a look.

Hi,
yes exactly.

There's an upstream issue in CairoLS. I'll try a workaround but in the meantime you could try opening Zed in the Cairo folder instead of the monorepo root.

For me it's not a serious problem, I just tend to work a lot with monorepo structures.
And something I noticed as I migrated to Zed as my main IDE. If it's fixable, then better.
Thank you