The Request class rework

PHP Code:

class Request
{
    /**
    * @var array
    */
    protected $data = [];

    /**
    * Get data from collection by key and request method
    * @param string $key
    * @return mixed
    */
    public function __get(string $key){}

    /**
    * Set data for outgoing request
    * @param string $key
    * @param string $value
    */
    public function __set(string $key, string $value){}

    /**
    * Get data from collection by key and request method
    * Default value can be set
    * @param string $key
    * @param null $default
    * @return mixed
    */
    public function get(string $key, $default = null){}

    /**
    * Get data collection by request method
    * @return array
    */
    public function getAll(){}

    /**
    * Get data from a query string
    * @param string $key
    * @param null $default
    * @return mixed
    */
    public function query(string $key, $default = null){}
} 


PHP Code:

class IncomingRequest extends Request
{
    /**
    * Disable the ability to set data for incoming requests
    */
    public function __set(string $key, string $value){ return null;}
} 


PHP Code:

//url host/path/?a=1&b=2&c=3 with POST method a=2&b=3

echo $request->a; // 2  alias for get('a'); 
echo $request->b; // 3
echo $request->get('a'); // 2
echo $request->get('c', 4); // 4
echo $request->getAll(); // ["a" => 2, "b" => 3]
echo $request->query('a'); // 1
echo $request->query('b'); // 2

//no more getGet, getPost, getGetPost, getPostGet, etc
//no filtering data, only raw 


It's only my opinion, but I find it even more confusing... I don't see that as an improvement. Your get() method returns data from $_POST. Why not from $_GET? What's the use case for get('c', 4) if it completely ignores c and always return 4?

CodeIgniter 4 tutorials (EN/FR) - https://includebeer.com
/*** NO support in private message - Use the forum! ***/

I feel your APIs are a bit cleaner, but
I'm not sure what the benefit would be to change the current APIs.
As includebeer says it may be more confusing for the current users.

Also, what about compliance with PSR-7?

ci-phpunit-test | CodeIgniter Testing Guide | CodeIgniter 3 to 4 Upgrade Helper

It's only my opinion, but I find it even more confusing... I don't see that as an improvement. Your get() method returns data from $_POST. Why not from $_GET?  What's the use case for get('c', 4) if it completely ignores c and always return 4?

Thank you. Maybe I forgot, but it seems to me that this is the first time I get feedback on this forum thread.

It seems to me that a possible reason why you do not understand why the get() method works with _POST, and not with _GET, is that you see the http method in the basis of the request, and I see the data.
The get() method works with the current HTTP method. Be it GET/POST/PUST/DELETE/PATCH/etc
That is, get() ! == _GET. get() === get the request data.

get('c', 4) returns 4 because there is no "c" parameter in the current POST request. Therefore, the get() method returns a default value.

---

I feel your APIs are a bit cleaner, but
I'm not sure what the benefit would be to change the current APIs.
As includebeer says it may be more confusing for the current users.

Also, what about compliance with PSR-7?

I have already commented on your PR. Let me explain. Now you cannot get the default value of a variable if it is not in the request. If the variable is not defined you will always get NULL. Although NULL may be one of the expected values.
Yes. Users may not immediately understand the nature of the changes.

PSR-7 does not regulate in any way how to get the request data.

Ok, now I understand your logic. But I'm still not sure it's an improvement of the current class. Maybe I'm old school, but I'm not a fan of magic stuff happening behind the scene. For me it's easier to understand what is going on if I call a function to retrieve the POST data or the GET data and not a function that will return one or the other depending on the http method.

CodeIgniter 4 tutorials (EN/FR) - https://includebeer.com
/*** NO support in private message - Use the forum! ***/

It seems to me that a possible reason why you do not understand why the get() method works with _POST, and not with _GET, is that you see the http method in the basis of the request, and I see the data.
The get() method works with the current HTTP method. Be it GET/POST/PUST/DELETE/PATCH/etc
That is, get() ! == _GET. get() === get the request data.

get('c', 4) returns 4 because there is no "c" parameter in the current POST request. Therefore, the get() method returns a default value.

I also did not understand your intent.

And I think the `get()` is difficult to understand, because its behavior changes in the context.
I prefer something like `getGet()`, `getPost()`, `getPut()`...

ci-phpunit-test | CodeIgniter Testing Guide | CodeIgniter 3 to 4 Upgrade Helper

1. Routes depend on the HTTP method.

PHP Code:

$request->get('resource', 'Controller::getRequest')
$request->post('resource', 'Controller::postRequest') 


2. Even if the route listens to multiple HTTP methods, the controller still has to separate the logic for different methods.

PHP Code:

$request->match(['get', 'post'], 'resource', 'Controller::request')
//... 
if ($this->request->getMethod() == 'post') { }
else { }
/* By the way, why are there no isPost/isGet/isMethodName methods yet? */ 


3. The IncomingRequest class already has a getVar() method, which is independent of the HTTP method.

Basically, you always want data sent by a specific HTTP method.
For example, you won't call getDelete() if there was a GET or POST or PUT request.

The only time to qualify a request method is any HTTP method other than GET + a query string.

iRedds

Your proposal is the same as Laravel, right?
https://laravel.com/docs/8.x/requests#re...nput-value

ci-phpunit-test | CodeIgniter Testing Guide | CodeIgniter 3 to 4 Upgrade Helper

iRedds

Your proposal is the same as Laravel, right?
https://laravel.com/docs/8.x/requests#re...nput-value

Yes you are right.

Symfony

    request: equivalent of $_POST;
    query: equivalent of $_GET ($request->query->get('name'));
    cookies: equivalent of $_COOKIE;
    attributes: no equivalent - used by your app to store other data (see below);
    files: equivalent of $_FILES;
    server: equivalent of $_SERVER;
    headers: mostly equivalent to a subset of $_SERVER ($request->headers->get('User-Agent')).

https://symfony.com/doc/current/componen...quest-data

CakePHP
https://book.cakephp.org/4/en/controller...parameters

Yii
https://www.yiiframework.com/doc/guide/2...parameters

Slim
https://www.slimframework.com/docs/v4/ob...quest-body

ci-phpunit-test | CodeIgniter Testing Guide | CodeIgniter 3 to 4 Upgrade Helper