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: fix wrong argument order when editing a subspace #1014

Merged
merged 4 commits into from
Oct 11, 2022

Conversation

dadamu
Copy link
Contributor

@dadamu dadamu commented Oct 11, 2022

Description

Closes: #XXXX
This PR fixes the argument order of EditSubspace message.


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)

@dadamu dadamu requested a review from a team as a code owner October 11, 2022 07:26
@github-actions github-actions bot added the x/subspaces Issue on the x/subspaces module label Oct 11, 2022
@RiccardoM RiccardoM changed the title fix: fixed edit subspace method fix: fix wrong argument order when editing a subspace Oct 11, 2022
Copy link
Contributor

@RiccardoM RiccardoM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job!

@RiccardoM RiccardoM added the automerge Automatically merge PR once all prerequisites pass label Oct 11, 2022
@codecov
Copy link

codecov bot commented Oct 11, 2022

Codecov Report

Base: 80.43% // Head: 80.41% // Decreases project coverage by -0.01% ⚠️

Coverage data is based on head (662fde6) compared to base (ded49cc).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1014      +/-   ##
==========================================
- Coverage   80.43%   80.41%   -0.02%     
==========================================
  Files         176      176              
  Lines       15379    15380       +1     
==========================================
- Hits        12370    12368       -2     
- Misses       2470     2472       +2     
- Partials      539      540       +1     
Impacted Files Coverage Δ
x/subspaces/keeper/msg_server.go 88.35% <100.00%> (-0.48%) ⬇️
app/app.go 88.19% <0.00%> (+0.01%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@mergify mergify bot merged commit 4c8449c into master Oct 11, 2022
@mergify mergify bot deleted the paul/fix-edit-subspace-method branch October 11, 2022 15:46
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/subspaces Issue on the x/subspaces module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants