Currently, for ewoks-orange widgets, when a task is provided with a pydantic model, its typing is taken into account when checking link types.
However, when a field validator exists — as in the darfix example — only the declared field types are taken into account, even if the validator effectively "extends" the set of accepted types.
It would be good to take validators into account as well (implicitly if possible, or otherwise by allowing them to be redefined).
Currently, for ewoks-orange widgets, when a task is provided with a pydantic model, its typing is taken into account when checking link types.
However, when a field validator exists — as in the darfix example — only the declared field types are taken into account, even if the validator effectively "extends" the set of accepted types.
It would be good to take validators into account as well (implicitly if possible, or otherwise by allowing them to be redefined).