Parsing Issue with Custom Type in `Constants` view

There seems to be some parsing error when using a custom struct in the constants tab of the Polkadot JS Apps.

There might be a bug in Polkadot JS Apps, but in general here is the steps to get what I think you want.

We have a custom type:

#[derive(Encode, Decode)]
struct Rule {
    name: Vec<u8>,
    version: u32,
    ops: Vec<u32>,
}

We place a const in the decl_module so it exposes it in the metadata:

         /// Rules for the PoE
        const rule: Rule = Rule {
            name: b"rule 1".to_vec(),
            version: 1,
            ops: vec![2]
        };

Then we start our chain. In Polkadot JS Apps, I register a new custom type:

{
  "Rule": {
    "name": "Vec<u8>",
    "version": "u32",
    "ops": "Vec<u32>"
  }
}

Then I go look at the constants in the pallet:

It seems it does not correctly detect the length prefix. When i parse the bytes on my own, it works:

[shawntabrizi]

can confirm it is fixed

thanks!

[jacogr]

Should be in apps in around 20 mins - if that doesn’t solve it, can re-open, but should be correct now. (Should have been fixed originally instead of hacked around for bytes-only)

Yes, as expected, the above based on the original API logic wouldn’t have parse correctly. (And your test was incorrect as well since it worked with partial data, i.e. the hex outputs never include the full picture, here is an additional length prefix in-front since it comes in as Vec<u8> in the metadata. So the UI actually did the correct thing based on what it was fed, and it was fed something wrong. And when it displayed, it also dropped the hex, which is then what you used as an input)