[wp-meta] [Making WordPress.org] #5303: Block plugin validation tool UI improvements

[Making WordPress.org]

#5303: Block plugin validation tool UI improvements
------------------------------+---------------------
 Reporter:  tellyworth        |       Owner:  (none)
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by JeffPaul):

 I caught this question in the #core-coding-standards channel and wasn’t
 sure if this was an odd case we should consider with the checker?
 https://wordpress.slack.com/archives/C5VCTJGH3/p1596239699173000
 > I just ran my plugin through the new Block Checker and it's giving a
 Fatal Error with this reason: Found PHP call header(). This is likely to
 prevent your plugin from working as expected. It's referring to this code
 at the top of the plugin:
 >
 > if (!defined('ABSPATH')) {
 >  header('Status: 403 Forbidden');
 >  header('HTTP/1.1 403 Forbidden');
 >  exit();
 >}
 >
 > It was in my understanding that this is always a good thing to put at
 the top of a plugin or theme in order to avoid direct access. Why would
 this be considered a Fatal Error ?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5303#comment:61>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org