Why removing the optimize in cargo.toml?

[bbqaaq]

Starting the commit #17 , this

[emidev98]

Hello @bbqaaq, there is an issue on going with some library versions. You can find more context here #19

[bbqaaq]

So may I ask if terrain will support workspace later? Currently terrain got problems with multi-contracts
or workspace setup.

Indeed I got problems with the terrain setup, as workspace is not working with current terrain.
See iboss-ptk/terrain#26 and I do some suggestions here.

#19 won't convince me to remove the optimize command, unless the repo one can cover 100% cases of usage.
I just need to override the #17 change and revert the code on my local machine terrain.

[bbqaaq]

@emidev98 Can you please not just close my issue? As Im telling some actual usage during development.
Workspace setup for contract development is common, and now it's not working with that.

I have my own optimize script to deal with it, and if this feature is officially close, I will just need to modify it on my local machine forever.

[emidev98]

Hey @bbqaaq,

I have seen that the original issue you opened is on the iboss-ptk repository and there is no support to that repository from here. Regarding the PR you have had to revert I understand your concerns, as you can imagine Terrain needs to provide the best experience for the developers and #17 was necessary to do not mix 0.16 with 1.0.0-beta packages (from cosmwasm).

Aside of that as you have a custom integration of terrain if you like you can create a proposal like this one #39 to integrate your custom feature to the main repo.

Regards,
Emi

[bbqaaq]

Thanks Emi.

I will gather my way of tackling workspace problem.
Will submit a PR to this repo once Im ready.

[emidev98]

Cool! Thank you everyone is welcome to collaborate to the repo