FlowPattern does not distinguish between numeric and string fields about models HOT 3 CLOSED

In the sample a pattern is being assigned to the field.
Also it will be up to the code generator to create whatever names it wants for classes, when the payload gets serialized to json there will be no named pattern, just a choice and a child property that details the choice.

from models.

Agree with not having to worry about named pattern when on wire (or serialized to json).

The problem I noticed was that I had to cast the field values to str() while creating the config - this does not affect all use cases though. e.g.

# from scapy
v1 = Dot1Q(id=[1, 3, 5])
# had to use
v2 = FlowVlan(id=NumField(choice='list', list=[str(id) for id in v1.id]))
# instead of
v2 = FlowVlan(id=NumField(choice='list', list=v1.id)) 

I figured we might come across more such hiccups.

from models.

At this time we are only supporting string values for field patterns.

from models.