Open pacmanifold opened 1 year ago
I guess two other ideas (maybe more solid?) could be:
cosmwasm_std::entry_point
in the workspace members to determine which are CosmWasm contractsCargo.toml
file specifying which members should be optimizedHey @pacmanifold! Always happy to hear user-stories like that 😄
Thanks for the contribution. I think it makes sense, with the caveat that there surely exists many projects that aren't virtual but still have a contracts/
folder. So we need to make sure we're not introducing a breaking change for existing users
@mandrean I found this today and it has already improved my life quality significantly. Thank you 🙏
But I ran into some issues when trying to compile "single contract repos" since they usually don't contain a
contracts
folder. Currently when runningcargo cw-optimizoor
in a single contract repo it results inTo reproduce run:
This PR solves this problem by only filtering the workspace members if the workspace is virtual. Does this seem like a reasonable to you?