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

fix: simplify x/relationships store keys #838

Merged
merged 3 commits into from
Apr 26, 2022

Conversation

RiccardoM
Copy link
Contributor

@RiccardoM RiccardoM commented Apr 22, 2022

Description

This PR updates the x/relationships store keys to use single bytes instead of string prefixes, to slim the storage space.


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 in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • 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 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)

@RiccardoM RiccardoM changed the title fix!: simplify x/relationships store keys fix: simplify x/relationships store keys Apr 22, 2022
Signed-off-by: Riccardo Montagnin <[email protected]>
@RiccardoM RiccardoM mentioned this pull request Apr 22, 2022
19 tasks
@codecov
Copy link

codecov bot commented Apr 22, 2022

Codecov Report

Merging #838 (8eea615) into master (c684768) will decrease coverage by 0.07%.
The diff coverage is 73.52%.

@@            Coverage Diff             @@
##           master     #838      +/-   ##
==========================================
- Coverage   81.53%   81.45%   -0.08%     
==========================================
  Files          89       90       +1     
  Lines        7018     7086      +68     
==========================================
+ Hits         5722     5772      +50     
- Misses       1035     1047      +12     
- Partials      261      267       +6     
Impacted Files Coverage Δ
x/relationships/legacy/v2/store.go 73.52% <73.52%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ef1a5b...8eea615. Read the comment docs.

Signed-off-by: Riccardo Montagnin <[email protected]>
@RiccardoM RiccardoM added the automerge Automatically merge PR once all prerequisites pass label Apr 22, 2022
@RiccardoM RiccardoM merged commit 57fd3fe into master Apr 26, 2022
@RiccardoM RiccardoM deleted the riccardo/update-relationships-keys branch April 26, 2022 08:51
RiccardoM added a commit that referenced this pull request May 16, 2022
## Description

This PR adds the spec folder inside the `x/relationships` module, containing the whole specification.

Depends-On: #829
Depends-On: #838

---

### 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...

- [x] 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
- [x] targeted the correct branch (see [PR Targeting](https://github.com/desmos-labs/desmos/blob/master/CONTRIBUTING.md#pr-targeting))
- [ ] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://docs.cosmos.network/v0.44/building-modules/intro.html)
- [ ] included the necessary unit and integration [tests](https://github.com/desmos-labs/desmos/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
- [x] reviewed "Files changed" and left comments if necessary
- [x] 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
Labels
automerge Automatically merge PR once all prerequisites pass x/relationships
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants