Good afternoon
it's great that you offer the Source Code for some Libraries like OkHttpUtils2 / iHttpUtils2 / HttpUtils2.
This allows us to fix annoying and unexpected issues like the fact, that the Http Utils do not give back the Http status code and, even worse, the proposed workaround is to manually patch the source and misuse the Tag property.
It took me about 15 minutes to correct the issue and now, HttpJob has the ErrorReason and StatusCode property. As users expect it.
But I am not willing to publish Source Code in a Forum where Users have to read all Forum-Posts to see if there is a new Release, download zip-Files and read the code to see if the currently used version is up to date (just because the zip file has no version information), etc.
Therefore:
please think about using GitHub or a similar service for your Open Source Projects. This would allow us to easily contribute and it's easier for you, to merge contribution (if you will keep an eye on changes).
Kind regards,
Thomas
it's great that you offer the Source Code for some Libraries like OkHttpUtils2 / iHttpUtils2 / HttpUtils2.
This allows us to fix annoying and unexpected issues like the fact, that the Http Utils do not give back the Http status code and, even worse, the proposed workaround is to manually patch the source and misuse the Tag property.
It took me about 15 minutes to correct the issue and now, HttpJob has the ErrorReason and StatusCode property. As users expect it.
But I am not willing to publish Source Code in a Forum where Users have to read all Forum-Posts to see if there is a new Release, download zip-Files and read the code to see if the currently used version is up to date (just because the zip file has no version information), etc.
Therefore:
please think about using GitHub or a similar service for your Open Source Projects. This would allow us to easily contribute and it's easier for you, to merge contribution (if you will keep an eye on changes).
Kind regards,
Thomas