[wp-trac] [WordPress Trac] #49341: Justify curl (and other) exceptions when submit plugin

[WordPress Trac]

#49341: Justify curl (and other) exceptions when submit plugin
-----------------------------+-----------------------------
 Reporter:  123milliseconds  |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Plugins          |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 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.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49341>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform