class TestlinkAPIClient implements in Release 0.4.0 not all api methods, which TL supports. Examples for missing implementations are
Although shows commit 9e1e092, that sometimes a combination of different optional arguments is needed, as TestlinkAPIClient support it currently.
Maybe a generic api class (TestlinkAPIGeneric) for the communication with TL, which supports all api method in a generic way and allows to transfer different optional parameter combinations, could help.
Problem would be the preparation of the results, like TestlinkAPIClient currently does in an accepted way. An approach would be, that TestlinkAPIClient inherits some generic behaviour (like error handling and so on) from the generic api class and still offers it special method. If somebody needs to call different method/parameters, he/she could use the generic api and must prepare the result be her/him self
class TestlinkAPIClient implements in Release 0.4.0 not all api methods, which TL supports. Examples for missing implementations are
Although shows commit 9e1e092, that sometimes a combination of different optional arguments is needed, as TestlinkAPIClient support it currently.
Maybe a generic api class (TestlinkAPIGeneric) for the communication with TL, which supports all api method in a generic way and allows to transfer different optional parameter combinations, could help.
Problem would be the preparation of the results, like TestlinkAPIClient currently does in an accepted way. An approach would be, that TestlinkAPIClient inherits some generic behaviour (like error handling and so on) from the generic api class and still offers it special method. If somebody needs to call different method/parameters, he/she could use the generic api and must prepare the result be her/him self