You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried to add other dexterity fields then e.g. textline or uri to a content_type uml.
(Relation, NamedBlobFile, ...)
these are not placed in the content_type interface.
but they are placed in the content_type implementation class if i decide to in the content_type uml via create_contentclass = true.
looks like, in dxgenerator.py line 275 is the "problem":
this moves only zope.schema.* fields to the interface class, but Relation field, etc isn't from there. so this stays in the content class (and becomes deleted afterwards, if create_contentclass = false)
I've tried to add other dexterity fields then e.g. textline or uri to a content_type uml.
(Relation, NamedBlobFile, ...)
these are not placed in the content_type interface.
but they are placed in the content_type implementation class if i decide to in the content_type uml via create_contentclass = true.
looks like, in dxgenerator.py line 275 is the "problem":
this moves only zope.schema.* fields to the interface class, but Relation field, etc isn't from there. so this stays in the content class (and becomes deleted afterwards, if create_contentclass = false)
i've tried and tested it without the
and it works as a charm.
any suggestions why only zope.schema fields should be allowed?
thanks
The text was updated successfully, but these errors were encountered: