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
Having to always denote the same xml properties over and over again, namely the prefix and the namespace on properties and data types alike, one should instead be able to add an xml property at the top level, e.g.
This then would act as the default for all data types and properties and also items of properties of type array.
This will make things much easier for us.
In the future, this could be extended so that one could have multiple NSURLs and associated prefixes and just reference these prefixes from xml code generation hints at the data type level or property level, e.g.
Having to always denote the same xml properties over and over again, namely the prefix and the namespace on properties and data types alike, one should instead be able to add an
xml
property at the top level, e.g.This then would act as the default for all data types and properties and also
items
of properties of typearray
.This will make things much easier for us.
In the future, this could be extended so that one could have multiple NSURLs and associated prefixes and just reference these prefixes from
xml
code generation hints at the data type level or property level, e.g.The code generator could then look up the prefix from the top level xml code generation hints and fill in the gaps.
The text was updated successfully, but these errors were encountered: