Conversation
f8b1984 to
5125ccb
Compare
5125ccb to
19717ce
Compare
|
@ccamel The migration wasn't working since paramspace is immediately initialized with the new params key table at the keeper instantiation before the migration run. Even with a legacy param subspace, we cannot change the registered key table (with the old one) at the migration step. So it impossible to get the old ParamsSet before migration to update it. Otherwise the FYI @amimart. |
|
@bdeneux This is excellent! Thanks for the improvement. |
aaa49f5 to
f44d280
Compare
amimart
left a comment
There was a problem hiding this comment.
Excellent! Everything seems fine 😉
bdeneux
left a comment
There was a problem hiding this comment.
Here my test to check if everything work 😜 :
- query logic
params(through CLI) - query logic
ask(CLI) - migration from old
x/paramto module state and new renamed params - update new params through a
"@type": "/logic.v1beta2.MsgUpdateParams"governance proposal
All good 👍 thank :)
|
All right! Thanks so much guys. ❤️ |
|
🎉 This PR is included in version 5.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Purpose
Implements #313. With this implementation, one can specifies a
predicates_blacklistof predicates to exclude from the set of registered predicates that theInterpretercan use. In addition, theregistered_predicatesparameter is renamed topredicates_whitelistfor consistency.Implementation details
<predicate_name>/[<arity>]strings. If a predicate name without arity is included in this list, then all predicates with that name will be considered regardless of arity.Consideration
proto. The code that performs the migrationv2tov3is included in the PR.Todo