Improved Enum support

[amorenoz]

Currently strong enum typing is not supported. #147 added type alias (e.g: type Alias = string) but, as discussed in that PR, that does not really enforce strong typing limitations.
For that to work we would need to to modify the ovsdb.bindings and mapper layers to cope with named-types.

Once core functionality is added, apart from nice enum validation, we can change replace the type alias with named-types in the generator and should be transparent to clients

[dave-tucker]

In addition, we should also adjust generation for Enum Sets so:

• In cases where min = 0 && max = 1 we should use a pointer to an Enum Type
• In cases where min = 1 && max = 1 we should use the Enum Type directly (note: I'm not sure if that will give us any compile time safety to ensure the value is not nil)

[amorenoz]

* In cases where `min = 0 && max = 1` we should use a pointer to an Enum Type

Maybe that idea can be applied to all sub-types (i.e: not only Enum)?
Lots of other columns also use this "pattern". e.g:

    "Logical_Router": {
      "columns": {
        "enabled": {
          "type": {
            "key": "boolean",
            "min": 0
          }
        },
...

In cases where min = 1 && max = 1 we should use the Enum Type directly (note: I'm not sure if that will give us any compile time safety to ensure the value is not nil)

I'd say this is already de behavior, isn't it?

[dave-tucker]

Yes that's a good point. Lets open another issue to track that. It should be easier to do once we've made the changes to the mapper to handle pointers for enum type objects.

…

On Tue, 13 Jul 2021, 07:51 Adrián Moreno, ***@***.***> wrote: * In cases where `min = 0 && max = 1` we should use a pointer to an Enum Type Maybe that idea can be applied to every type (i.e: not only Enum)? Lots of other columns also use this "pattern". e.g: "Logical_Router": { "columns": { "enabled": { "type": { "key": "boolean", "min": 0 } }, ... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#154 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA43JEKOPATASWONVQBN3KTTXPO65ANCNFSM46OTZVNQ> .

[amorenoz]

#191