I'm submitting a
Current Behaviour:
We are using the keyword arguments to add range to supported property, which is fine. But users may not always use xsd:float/integer, while defiining properties.
Expected Behaviour:
It might be useful to have a separate datatype argument in docwriter while creating a new supportedProperty, which we map directly to xsd:float/integere instead of using the keyword arguments to specify the datatype.
We should give them an option define the datatype using python datatypes which we add to range as xsd:float/integer and let that behaviour be overridden with kwargs instead of relying on kwargs only.
I'd like to hear thoughts on this, it should be a small addition.
Steps to reproduce:
Do you want to work on this issue?
I'm submitting a
Current Behaviour:
We are using the keyword arguments to add
rangeto supported property, which is fine. But users may not always usexsd:float/integer, while defiining properties.Expected Behaviour:
It might be useful to have a separate datatype argument in docwriter while creating a new supportedProperty, which we map directly to
xsd:float/integereinstead of using the keyword arguments to specify the datatype.We should give them an option define the datatype using python datatypes which we add to
rangeasxsd:float/integerand let that behaviour be overridden with kwargs instead of relying on kwargs only.I'd like to hear thoughts on this, it should be a small addition.
Steps to reproduce:
Do you want to work on this issue?