ComputedFieldInfo needs some love (no exclude, no default arguments)

[devkral]

ComputedFieldInfo needs some love (no exclude, no default arguments)

[sydney-runkle]

@devkral,

Thanks for the requests. I'd say anything we can do to make it more similar to the FieldInfo constructor would be welcome.

The exclude stuff might be tricky due to when that happens at serialization time, but definitely something worth looking into.

Perhaps you could provide some examples of what your last two requests might look like?

[devkral]

sry, for the late answer, was deep in coding.

The constructor doesn't contain default arguments like it does in FieldInfo.

The exclude stuff should work like it is documented for normal fields.

[devkral]

Pseudo python Code:

class Foo(ComputedFileInfo):
  def __init__(self, wrapped_property, **kwargs):
    kwargs.setdefault("exclude", False)
    super().__init__(self, wrapped_property=wrapped_property, **kwargs)

# And:
foo().metadata should exists, so if someone iterates through properties he doesn't fall over.
# Or maybe we can add some info here

should be possible. The exclude is an example for kwargs could be transformed.

[devkral]

why do we want exclude? Of course you can have normal properties which are excluded but maybe you want the metainformation.