SNIP-12 can't create a merkletree of enums

[sgc-code]

Describe the bug
Regarding SNIP-12.
It doesn't seem to be possible to create a merktree of enum

To Reproduce
I'm not sure what would be the correct types, but i tried these two approaches with no luck

{
  StarknetDomain: [ ... ],
  Object: [{ name: "tree", type: "merkletree", contains: "MyEnum" }],
  MyEnum: [{ name: "Variant 1", type: "()" }]
}

{
  StarknetDomain: [ ... ],
  Object: [{ name: "tree", type: "merkletree", contains: "enum" }],
  MyEnum: [{ name: "Variant 1", type: "()" }]
}

Expected behavior
There should be a way to create a merkle tree of any type, including enums

Screenshots

Desktop (please complete the following information):

Node version: 18
Starknet.js version: v6.23.1 (latest)

Additional context

[penovicp]

For something to be recognized as an enum or merkletree entry it needs to have the type property, so to use both something like the following should be possible:

    "Tree":   [{ "name": "root", "type": "merkletree", "contains": "Leaf" }],
    "Leaf":   [{ "name": "someEnum", "type": "enum", "contains": "MyEnum" }],
    "MyEnum": [{ "name": "Variant 1", "type": "()" }]

[sgc-code]

For something to be recognized as an enum or merkletree entry it needs to have the type property

No sure what you mean @penovicp , in this example both types have a type

{
  StarknetDomain: [ ... ],
  Object: [{ name: "tree", type: "merkletree", contains: "MyEnum" }],
  MyEnum: [{ name: "Variant 1", type: "()" }]
}

[penovicp]

Neither has type: "enum".

[sgc-code]

Neither has type: "enum".
@penovicp correct,
but any reason why that shouldn't work? the spec doesn't say anything about disallowing enums

[penovicp]

A node of type: "enum" and a node defining its variants are what constitutes an enum in the spec, the two nodes together.

With the type name constraints that were adopted after the enum format was defined, namely the prohibition of using commas and parentheses within the names, it would be theoretically possible to omit the root enum node but that would mean changing the spec.