Both the v2.2 and v2.3 updates are due to test issues that were triggered by minor changes in the API. Although the changes technically do not affect the usage of the library, they do cause build/test issues in Travis.
Revamping the test.py with less specific tests as was originally done in the v1/Legacy API would be the logical option. One APIs result was essentially fed into another. This more closely represented the general use case, as well as exercised more of the code/higher coverage.
Both the v2.2 and v2.3 updates are due to test issues that were triggered by minor changes in the API. Although the changes technically do not affect the usage of the library, they do cause build/test issues in Travis.
Revamping the
test.py
with less specific tests as was originally done in the v1/Legacy API would be the logical option. One APIs result was essentially fed into another. This more closely represented the general use case, as well as exercised more of the code/higher coverage.