Kayanski

> Framework tests seem to be failing but I think this was fixed in the interchain improvement PR! I confirm this is fixed in https://github.com/AbstractSDK/abstract/pull/474

> I'm surprised by how much code was changed for this feature, and it's breaking to cw-orch-core. > > is there no alternative way that we could structure this PR...

This PR is breaking to cw-orch-core and won't be merged anytime soon. Keeping it as an Issue for tracking purposes

> Since it removes reply ids entirely, how would developers build examples with dynamic replies like: > > https://github.com/CyberHoward/interchain-gov/blob/main/contracts/interchain-gov/src/contract.rs#L37-L45 They wouldn't, but using ID as a value field shouldn't not...

> > Since it removes reply ids entirely, how would developers build examples with dynamic replies like: > > https://github.com/CyberHoward/interchain-gov/blob/main/contracts/interchain-gov/src/contract.rs#L37-L45 > > And makes it more difficult to migrate existing...

This was a POC, closing as this introduces too much complexity for very little gain

It's still an issue when you are working with `rust-analyzer`, is there a way to fix that and for the library to choose one library ?

Bumping this because our [staking and dex adapters](https://github.com/AbstractSDK/abstract/blob/d7e7e04965b4bba999f287d124d8aa3d8ad45ccd/modules/contracts/adapters/dex/Cargo.toml#L33) feel very lonely