Symfony version(s) affected: 5.1

Description
It is possible to pass request parameters of any type to the Symfony web crawler, something that's not possible in actual requests.

How to reproduce
On the sending end:

        $client = static::createClient();
        $client->request('POST', '/endpoint', [
            'foo' => 'bar',
            'baz' => 1.1,
        

So if you happen to insert invalid version string when requiring package, it will still write it into composer.json and nothing works after that. So for example; composer require phpunit/phpunit:"8.3.3 as ^8.3"

My composer.json:

{
    "require": {
        "phpunit/phpunit": "8.3.3 as ^8.3"
    }
}

Output of composer diagnose:

$ composer diagnose
        

According to http://manual.phpdoc.org/HTMLframesConverter/default/

@property shows a "magic" property variable that is found inside the class.

The property is presumed to be available for both read and write operations. If the property is read-only, you should use the @property-read tag instead. If the property is write-only, use @property-write.

Example:

/**
 * show

As it looks for me, there is no no way to access the Access Control List (ACL) feature for folder by remotecontrol.
I would expect it in OCS API. But i cannot find it.

Can you implement it?

This is my use case:
I program in a small team a software to generate template structures in nextcloud for similar workgroups on different locations. They have all the same workflow.
E.g. if a new wo

Under the 'Theme' settings tab you can upload images. It would be great if vector images can be added so it can scale without causing artifacts.

• OctoberCMS Build: 466
• PHP Version: 7.2^
• Database Engine: MySQL MariaDB 10.3.23 (with strict set to true through database.php configuration)

Description:

For one of our plugins we're currently running into the error described below:

SQLSTATE[42000]: Syntax error or access violation: 1140 Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if th

When creating or editing a relationship, we should group the relationship type list with the same tag as on the contact page (Love, Family, Other kind, ...), i.e. with an element.