Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add metadata to Vote in x/gov #11268

Closed
4 tasks done
blushi opened this issue Feb 24, 2022 · 7 comments · Fixed by #11308
Closed
4 tasks done

Add metadata to Vote in x/gov #11268

blushi opened this issue Feb 24, 2022 · 7 comments · Fixed by #11308
Assignees

Comments

@blushi
Copy link
Contributor

blushi commented Feb 24, 2022

Summary

Add metadata to Vote in x/gov (should use the existing maxMetadataLen constraint).

Remove metadata field from Vote in x/group


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@aaronc
Copy link
Member

aaronc commented Feb 25, 2022

Why?

@blushi
Copy link
Contributor Author

blushi commented Feb 25, 2022

Why?

This was discussed during the last Gov / groups weekly sync with @cmwaters @hxrts @nooomski (notes) to align more with x/gov.

@aaronc
Copy link
Member

aaronc commented Feb 25, 2022

I guess we can add back later but the idea is to be able to support voting interfaces like Loomio where a voter can provide and explanation

@amaury1093
Copy link
Contributor

I guess we can add back later

Small note: Since it's in a Msg, I'm not sure it's easy to add later, unless we create a new Msg.

I don't have a strong opinion on add or not, but if we add, I would prefer:

@aaronc
Copy link
Member

aaronc commented Feb 28, 2022

Agree with change to string because of ledger signing UX. If we think there’s a use case for people describing their votes - which I actually think is good for governance - then we should have metadata for votes in both gov and group with a short character limit (maybe 128) long enough for a URL + hash

@hxrts
Copy link
Contributor

hxrts commented Feb 28, 2022

We either needed to add to gov or remove from groups and it seemed easier to do the later. Also there was some state bloat concern.

@blushi blushi changed the title Remove metadata from Vote in x/group Add metadata to Vote in x/gov Mar 1, 2022
@blushi
Copy link
Contributor Author

blushi commented Mar 1, 2022

FYI After our gov/group dev sync today, we aligned on adding metadata to Vote in x/gov instead, I've updated the issue description to account for that.

@mergify mergify bot closed this as completed in #11308 Mar 3, 2022
mergify bot pushed a commit that referenced this issue Mar 3, 2022
## Description

Closes: #11268 

Add metadata to Vote in x/gov using the existing maxMetadataLen constraint.

---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] added `!` to the type prefix if API or client breaking change
- [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#pr-targeting))
- [ ] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/master/docs/building-modules)
- [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#testing)
- [ ] added a changelog entry to `CHANGELOG.md`
- [ ] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [ ] updated the relevant documentation or specification
- [ ] reviewed "Files changed" and left comments if necessary
- [ ] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

5 participants