When writing extractors, we are encountering a few issues with the 'other' field under the Binary class.
Namely
single strings/ints are not allowed
lists of ints are automatically converted to lists of strings by pydantic (!) as it selects the first compatible type
from memory there is a pydantic settings to change this behaviour
We have some more complex data types which require a dictionary
e.g. "taken_from": {"value": "variant-a", "offset": 394, "size": 13}
I think it would be useful for the typing of this field to match the typing for ExtractorModel.other. As this is loosening the typing rather than restricting, there should be no incompatibility with existing extractors.
When writing extractors, we are encountering a few issues with the 'other' field under the Binary class.
Namely
"taken_from": {"value": "variant-a", "offset": 394, "size": 13}I think it would be useful for the typing of this field to match the typing for ExtractorModel.other. As this is loosening the typing rather than restricting, there should be no incompatibility with existing extractors.