IBX-10458: Implemented new Content Type search PHP API

[barw4]

🎫 Issue	IBX-10458

Caution

Table/column names/aliases mergup.

Description:

The ContentTypeService contract has been extended with a new method:

    public function findContentTypes(?ContentTypeQuery $query = null, array $prioritizedLanguages = []): SearchResult;

The ContentTypeQuery object receives the following arguments:

        ?CriterionInterface $criterion = null,
        array $sortClauses = [],
        int $offset = 0,
        int $limit = 25

And the available criterions are:

• ContainsFieldDefinitionIds (joins field definitions and validates if a content type contains them)
• ContentTypeGroupIds (joins content type group assignment table and searches for provided group ids)
• Identifiers (content type identifiers)
• Ids (content type ids)
• IsSystem (joins content type group table via content type group assignment table and validates if group is system or not)
• LogicalAnd
• LogicalOr
• LogicalNot

There are also available the following sort clauses:

• Ibexa\Contracts\Core\Repository\Values\ContentType\Query\SortClause\Id
• Ibexa\Contracts\Core\Repository\Values\ContentType\Query\SortClause\Identifiers

Examplary query:

            new ContentTypeQuery(
                new LogicalOr([
                    new LogicalAnd([
                        new ContentTypeIdentifier(['folder', 'article']),
                        new ContentTypeGroupId([1]),
                    ]),
                    new ContentTypeIdentifier(['user']),
                ]),
            ),

For QA:

Documentation:

[adamwojs]

Let's focus first on establishing final shape of the contracts.

[Steveb-p]

Why is sorting done on the second query, not on the one where you actually acquire IDs?

When done in the 2nd query, assuming that LIMIT caused later results to be discarded, the order of results will be incorrect.

[barw4]

Isn't it the opposite? When I sort in the first query, I get sorted ids, correct. But do I have a guarantee that results in second query are sorted when fetched with WHERE IN and without a sort clause? Tests show that I need to sort the second query.

[ViniTou]

Is there an easy way to make it either array or int and not both? Would that provide to many limitations?

[barw4]

We could potentially create second property and type it properly, but I'm not sure if that won't overcomplicate stuff

[ViniTou]

remember that we also changed those aliases - either, if possible, rename them now to ibexa_ or if those relay on exsiting mappers - remember to do it on mergeup.

[barw4]

They rely on the mappers, but I'll keep in mind to change it during mergup, thanks!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud