`anchor init` should consider already existing workspace

[ranile]

Cargo doesn't support nested workspaces. When anchor init is run, it unconditionally creates a new workspace and members of that workspace.

It should try to find an existing workspace. If one exists, that workspace should be used. Otherwise a new workspace should be created

[etimofeeva]

could you please assign that to me, please?

[4ddx]

Hi, seems like this is still open.

Can I be assigned this issue?

[calmw]

这个问题，你们解决了吗？ 我现在使用anchor的时候，依然是这样

[spellsaif]

you can use

  anchor new program_name

it will create new program in current workspace.

If this is not what you meant, can you explain it more?

[ajey35]

hey @ranile i think it is resolved !
see this
if !force && Config::discover(cfg_override)?.is_some() { return Err(anyhow!("Workspace already initialized")); }
here the erros message is display when you try to run anchor init in same already initilized path!

[ajey35]

check here it is already fixed

https://github.com/solana-foundation/anchor/blob/master/cli/src/lib.rs

[M2iC2H2A2L]

Interested in this issue! Planning to work on a PR for better workspace handling. Any quick tips?

[bit2swaz]

quick question: is the intended fix here to make anchor init reuse an existing parent Cargo/Anchor workspace instead of erroring or nesting a new one, or is anchor new now considered the preferred workflow?