Add listKey argument to DoctrineListRepresentationFactory and DoctrineNestedListRepresentationFactory

[luca-rath]

Currently those classes only work properly, if the LIST_KEY and the RESOURCE_KEY are equal. If this is not the case, you would have to do something like the following, to make it work:

public function cgetAction(Request $request): Response
{
    $listRepresentation = $this->doctrineListRepresentationFactory->createDoctrineListRepresentation(
        self::LIST_KEY, // Note that this argument is named $resourceKey
    );

    $listRepresentation = new PaginatedRepresentation(
        $listRepresentation->getData(),
        self::RESOURCE_KEY,
        $listRepresentation->getPage(),
        $listRepresentation->getLimit(),
        $listRepresentation->getTotal(),
    );

    return $this->handleView(
        $this->view($listRepresentation)
    );
}

With this pull request, the code can be simplified to the following:

public function cgetAction(Request $request): Response
{
    $listRepresentation = $this->doctrineListRepresentationFactory->createDoctrineListRepresentation(
        self::RESOURCE_KEY,
        [],
        [],
        [],
        self::LIST_KEY,
    );

    return $this->handleView(
        $this->view($listRepresentation)
    );
}

[alexander-schranz]

We still should make sure that resource key and list keys are matching in our projects ;)

[luca-rath]

We still should make sure that resource key and list keys are matching in our projects ;)

Yes I agree, but there are edge cases where this is not possible. Recently we had a customer project, where a specific export list config was required, so there were two list configs for the same resource