Hello
@Suman Bagde.
On the CTK (Conformance Test Kit) the Mandatory parameters will be tested by the variable type. The optional parameters will not. Meaning: if you change the type of an optional variable you can still be conformant.
The limit and offset are not currently being used in any CTK, as mandatory or optional.
We have plans to have more levels of Conformance, for compliance on those new levels you will need to have the optional parameters the right variable type when those optional parameters are present. To my knowledge there are no discussion on enforcing the variable type of such parameters as limit and offset.
As
@Jonathan Goldberg said, those fields being integer make sense by the expected data they will hold. If you think we are overlooking some possibilities let us know.
Best Regards,
Henrique Rodrigues
------------------------------
Henrique Rodrigues
TM Forum
------------------------------
Original Message:
Sent: Mar 16, 2019 16:36
From: Jonathan Goldberg
Subject: Input parameters for API's
From a formal perspective, @Henrique Rodrigues can hopefully give you an answer regarding the behavior of the conformance kits.
But I am wondering why you would want to change the type - these fields have integer semantics and it is not clear (to me) what you would gain by making them strings.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Original Message:
Sent: Mar 15, 2019 01:52
From: Suman Bagde
Subject: Input parameters for API's
Hi All,
Some of the input parameters in the API operations are defined as integer.
Examples: limit, offset
Do they necessarily have to be integer's or can we change them to string in our implementation? Would we still be complaint?
Thank you.
------------------------------
Warm Regards,
Suman Bagde
------------------------------