Justify curl (and other) exceptions when submit plugin

[123milliseconds]

When I submitted a plugin the WordPress QA team suggested I raise a ticket - this is that ticket.

If you mean the curl, curl is acceptable BUT you have to document your code as to why. We also ask you make a ticket so WordPress corrects this.

I got impression after 2 tries to get plugin approved the QA auto scan source code and auto replies to me with list of problems.

I could not get anyone to look at code since I had code issues ... with curl.

Could we have some tag in source code where developers list reasons they use a 'forbidden' function ... like curl.

This tag needs to be in source code. Then QA team can see the problem case INSIDE the context of the source code.

Example:

justify ## Using CURL Instead of HTTP API

justify This plugin needs the curl total-time response from CURL
justify This curl time measure is the reason the plugin exists.
justify I cannot use the wp http api - it has no total-time.

[SergeyBiryukov]

Hi there, welcome to WordPress Trac! Thanks for the ticket.

Getting the total_time from cURL via WordPress HTTP API is possible using the requests-curl.after_request action hook, see #47659 for details, specifically comment:2:ticket:47659 for an example.

Please note that this Trac is used for enhancements and bug reporting for the WordPress core software. Any issues or ideas for WordPress.org sites, including the Plugin Directory, should be reported on ​https://meta.trac.wordpress.org.

I've transferred the report to ​#meta4999. Thanks again!