We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arguments to MAL operations can now be specified as named fields rather than just type information, i.e. from this:
<mal:submit> <mal:type name="Boolean" area="MAL"/> <mal:type list="true" name="InstanceBooleanPair" area="COM"/> </mal:submit>
to this:
<mal:submit> <mal:field name="isGroupIds"> <mal:type name="Boolean" area="MAL"/> </mal:field> <mal:field name="enableInstance"> <mal:type list="true" name="InstanceBooleanPair" area="COM"/> </mal:field> </mal:submit>
The name should be reflected in the generated API, especially in the get/set methods in the compound return classes.
The text was updated successfully, but these errors were encountered:
DavidFeliot
No branches or pull requests
Arguments to MAL operations can now be specified as named fields rather than just type information, i.e. from this:
to this:
The name should be reflected in the generated API, especially in the get/set methods in the compound return classes.
The text was updated successfully, but these errors were encountered: