Request dispatcher for PHP JSON web service Below you can find the constructor method and related fields of the main class of my REST API (note that the class contains more code than displayed) written in PHP 7.1. It does various things with the HTTP-request. It starts with getting the arguments and then it gets the method in which the request is made (like POST or GET). The request gets trimmed of tags and that gets saved back into the instance/member variable $this-&gt;request.

Now, to my best knowledge, $this-&gt;request in PHP always points to the HTTP-request when a HTTP-request has just been made. The code can only get here when a HTTP-request has been made and $this-&gt;method has been filled ($this-&gt;method = $_SERVER['REQUEST_METHOD'];). 

In other words, $this-&gt;method should always exist, but I keep getting the 'Field declared dynamically' warning:



Is it okay to just ignore the warning or is there a best practice to deal with it?

Other tips to improve my code are welcome too. I've 'learned' PHP  back in version 4 (I used it for uni once). I struggle with the OO concepts since introduced in a language where so much is allowed. 

class BaseAPI {

    protected $method = '';
    protected $endpoint = '';
    protected $verb = '';  
    protected $args = Array();  

    public function __construct($request)
    {
        header("Access-Control-Allow-Orgin: *");
        header("Access-Control-Allow-Methods: *");
        header("Content-Type: application/json");

        $this-&gt;args = explode('/', rtrim($request, '/'));
        $this-&gt;endpoint = array_shift($this-&gt;args);
        if (array_key_exists(0, $this-&gt;args) &amp;&amp; !is_numeric($this-&gt;args[0])) {
            $this-&gt;verb = array_shift($this-&gt;args);
        }

        $this-&gt;method = $_SERVER['REQUEST_METHOD'];
        if ($this-&gt;method == 'POST' &amp;&amp; array_key_exists('HTTP_X_HTTP_METHOD', $_SERVER)) {
            if ($_SERVER['HTTP_X_HTTP_METHOD'] == 'DELETE') {
                $this-&gt;method = 'DELETE';
            } else if ($_SERVER['HTTP_X_HTTP_METHOD'] == 'PUT') {
                $this-&gt;method = 'PUT';
            } else {
                throw new IncorrectHeaderException("Unexpected Header");
            }
        }

        switch ($this-&gt;method) {
            case 'DELETE':
            case 'PUT':
                // don't do anything yet
            case 'POST':
                $this-&gt;request = $this-&gt;_cleanInput($_POST);
                break;
            case 'GET':
                $this-&gt;request = $this-&gt;_cleanInput($_GET);
                break;
            default:
                throw new IncorrectMethodException('Invalid Method');
                break;
        }
    }

    private function _cleanInput($data)
    {
        $cleaned_input = Array();
        if (is_array($data)) {
            foreach ($data as $k =&gt; $v) {
                $cleaned_input[$k] = $this-&gt;_cleanInput($v);
            }
        } else {
            $cleaned_input = trim(strip_tags($data));
        }
        return $cleaned_input;
    }
}
Now, to my best knowledge, $this->request in PHP always points to the HTTP-request when a HTTP-request has just been made


My guess is that you are thinking of the super-global $_REQUEST? That is not the same as $this-&gt;request (unless somehow that instance variable gets set to something else)...


  Is it okay to just ignore the warning or is there a best practice to deal with it?


Declare the property, just as the other instance properties are declared (i.e. $method, $endpoint, $verb, etc.):

class BaseAPI {

    protected $request;


That way the IDE will know that the property should at least exist for each instance (though it might not be assigned a value until that switch statement).

Other Feedback

Switch statement cases:


switch ($this-&gt;method) {
        case 'DELETE':
        case 'PUT':
            // don't do anything yet



Those first cases are missing a break; so the PHP pre-processor will fall-through to the POST case.

header() calls in constructor

The three calls to header() in the constructor feels a little strange but then again it is difficult to know what the rest of your code looks like. Typically those would go in a method to render/send output.