-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Replace parameter_types
with ConstU32
&c.
#10383
Comments
Picking this up @gavofyork |
@gavofyork i see in your PR here #10382 that you have defined the implementation for ConstU64, ConstU128 and ConstBool. Only ConstU32 is available currently in master. Should i wait for your PR to get merged before solving this issue? |
You could just start on a branch which brings in that change. It's not a lot of code. |
When you say start on a branch, Are you saying i should start off on my own branch which I already started(changing parameter types for ConstU32)? More so, are you saying i should implement the |
Yes, you could copy that code in if it's going to be useful (and it probably is). |
I have started the implementation as opened in the PR |
Fixed by #10402. |
some place could still be replaced #10402 (comment) |
This issue is still open? @thiolliere |
@bizzyvinci have you checked the mentioned code? |
Yes. |
# Goal The goal of this PR is to reduce and remove code Split off of #1448 # Discussion - Turns out that parameter_types! is not needed as much anymore so removed a bunch of them (based on paritytech/substrate#10383 ) - Removed the need for custom implementations on `MaxSchemaGrantsPerDelegation` - Aligned the BlockNumber (old u64) in testing with the BlockNumber (u32) in production
Most simple
parameter_types
declarations can be replaced with the newConstU32
,ConstU64
,ConstU128
andConstBool
, reducing some unneeded verbosity.The text was updated successfully, but these errors were encountered: