[Issue] [PHPDOC] Fix bad phpdoc Magento\Eav\Model\ResourceModel\Entity\Attribute\Collection

[m2-assistant]

This issue is automatically created based on existing pull request: #39155: [PHPDOC] Fix bad phpdoc Magento\Eav\Model\ResourceModel\Entity\Attribute\Collection

---

Description (*)

This PR fix the bad phpdoc for \Magento\Eav\Model\ResourceModel\Entity\Attribute\Collection.

• joinLeft:
  • The first argument can be string or array<string, array>
  • The 3th argument can be string or array<string>

Here is an example where the type array is used :

magento2/app/code/Magento/Eav/Model/AttributeRepository.php

Lines 114 to 118 in d06337a

	$attributeCollection->joinLeft(
	['eav_entity_attribute' => $attributeCollection->getTable('eav_entity_attribute')],
	'main_table.attribute_id = eav_entity_attribute.attribute_id',
	[]
	);

For example, with PHPSTAN is very complicated to setup the project with level 5 or higher :(

Related Pull Requests

None

Fixed Issues (if relevant)

None

Manual testing scenarios (*)

Setup PHPSTAN with level 5 or higher and run check.

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-16187 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.