[wp-meta] [Making WordPress.org] #4999: Justify curl (and other) exceptions when submit plugin

Making WordPress.org noreply at wordpress.org
Sun Feb 2 15:32:41 UTC 2020

#4999: Justify curl (and other) exceptions when submit plugin
 Reporter:  123milliseconds   |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
 Trasferred from #WP49341.

 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

 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.


 // 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://meta.trac.wordpress.org/ticket/4999>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list