src/View/Requirements_Backend.php
public function block($fileOrID)
    {
        if (is_string($fileOrID)) {
            $fileOrID = ModuleResourceLoader::singleton()->resolvePath($fileOrID);
        }
        $this->blocked[$fileOrID] = $fileOrID;
    }
public function block($fileOrID)
    {
        if (is_string($fileOrID)) {
            $fileOrID = ModuleResourceLoader::singleton()->resolvePath($fileOrID);
        }
        $this->blocked[$fileOrID] = $fileOrID;
    }
public function block ( $ fileOrID ) { if ( is_string ( $ fileOrID ) ) { $ fileOrID = ModuleResourceLoader :: singleton ( ) -> resolvePath ( $ fileOrID ) ; } $ this -> blocked [ $ fileOrID ] = $ fileOrID ; }
Block inclusion of a specific file

The difference between this and {@link clear} is that the calling order does not matter;
{@link clear} must be called after the initial registration, whereas {@link block} can be
used in advance. This is useful, for example, to block scripts included by a superclass
without having to override entire functions and duplicate a lot of code.

Note that blocking should be used sparingly because it's hard to trace where an file is
being blocked from.

@param string|int $fileOrID Relative path from webroot, module resource reference or
requirement API ID
Block inclusion of a specific file