-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
refactor: remove .Type()
and .Route()
from msgs
#14751
Conversation
.Type()
and .Route()
from msgs
To backport or not to backport to v0.47.1, this is the question. There is no breaking change, neither feature change, only a cleanup. Except from one field removal in simulation. IMHO this is a good improvement. As we don't backport this for v0.47.0, I will just add the |
@@ -160,14 +160,6 @@ type TestEvidence struct{} | |||
|
|||
var _ exported.Evidence = &TestEvidence{} | |||
|
|||
func (*TestEvidence) Route() string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't delete this, as an evidence message has a route:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AMAZING!
@Mergifyio backport release/v0.47.x |
✅ Backports have been created
|
(cherry picked from commit 8dbdfea) # Conflicts: # CHANGELOG.md # x/distribution/types/msg.go # x/evidence/types/msgs.go # x/gov/client/utils/query_test.go # x/gov/simulation/operations.go # x/gov/simulation/operations_test.go # x/gov/types/v1/msgs.go # x/staking/simulation/operations_test.go
Description
Remove
.Type()
and.Route()
from all msgs and reflect that in the simulator.ref: #14728, #14753
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...
!
to the type prefix if API or client breaking changeCHANGELOG.md
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...
!
in the type prefix if API or client breaking change