_Scenario_:
I am using a type(complex or simple type like struct) which has a TypeConverter. I am using this type as a input parameter on my action. The values for this parameter are expected to come from Uri.
_Issue_:
HelpPage UI displays individual properties of this type, which would be confusing as users might not be using each of these individual properties in the Uri and also its inconsistent with the behavior of Enumerations, which also have type converter.
_Attached_ snapshots.
In case of 'Point', the request would be, for example, like : /api/values?pnt=10,20
Check CartType.png and you would notice that it doesn't list all of the individual properties in the page and instead only provides a link
I am using a type(complex or simple type like struct) which has a TypeConverter. I am using this type as a input parameter on my action. The values for this parameter are expected to come from Uri.
_Issue_:
HelpPage UI displays individual properties of this type, which would be confusing as users might not be using each of these individual properties in the Uri and also its inconsistent with the behavior of Enumerations, which also have type converter.
_Attached_ snapshots.
In case of 'Point', the request would be, for example, like : /api/values?pnt=10,20
Check CartType.png and you would notice that it doesn't list all of the individual properties in the page and instead only provides a link