Mykhailo Donchenko
Mykhailo Donchenko
Imagine that scenario: 1. We have a policy like that: ``` roles: [ { name: "all", kind: "Everyone", permissions: ["*:AddProposal", "*:VoteApprove"], vote_policy: {} } ]; ... default_vote_policy: { weight_kind: "TokenWeight",...
It's simple implementation of #237 query. What do you think @ezekiiel? Unsure if we should show created proposals too? How do i test gas usage? Via [cosmwasm-vm](https://crates.io/crates/cosmwasm-vm)? I can try...
Ok, I think it's just absolutely worse than #412. Can't see any advantage, except gas, when wallet did miss a lot of proposals. But wanted to share the idea anyway!...
Added ava tests. Run `test.sh`(on unix) or `test.bat` on windows for testing.
Updated counter example version 4.0.0-pre.2, changed account types, log to log_str, removed allocator, fixed tests
### Short description So, what happened: we have a lib that wants to import `voting`, and then contract depend on that lib, what happens: [cw-core](https://github.com/DA0-DA0/dao-contracts/blob/693a5d6a36ada1505c5a52e8029b1b80ea557393/packages/voting/Cargo.toml#L15) gets imported (with everything) ###...
For CI purposes it would be useful to use pre-compiled binaries, for example by using [cargo-quickinstall](https://github.com/cargo-bins/cargo-quickinstall) But this tool doesn't provide a way to enable vendored openssl to make sure...
Not sure if this is quickinstall issue, but it looks similar to #235, so I'll create an issue here. [cargo-workspaces](https://crates.io/crates/cargo-workspaces) library linked to shared OpenSSL libs: ``` # ldd from...
Tests for status message using [workspaces-rs](https://github.com/near/workspaces-rs). Just run `cargo test -- --nocapture` inside tests-workspaces/
While #26 is not merged, let's slightly update `README.md`, to not confuse users