Incorrect @var reference in docBlock of a class member variable

[salmanazeez786]

There is an incorrect @var reference in the doc block of the class member variable $queueIterator in class
\Magento\Framework\MessageQueue\Topology\Config

Preconditions (*)

1. Magento 2.3.x

Steps to reproduce (*)

1. Check the doc block of this class member variable \Magento\Framework\MessageQueue\Topology\Config::$queueIterator in file vendor/magento/framework-message-queue/Topology/Config.php

Expected result (*)

Actual result (*)

[m2-assistant]

Hi @salmanazeez786. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@salmanazeez786 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @shikhamis11. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-21708 were created

Issue Available: @shikhamis11, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[shikhamis11]

@salmanazeez786
Thank you for reporting this issue Please create Pull request for it's correction
you can check guide for contribution
https://devdocs.magento.com/guides/v2.3/contributor-guide/contributing.html

[ghost]

Thank you @p-bystritsky for proposing this as Good First Issue!
Community Maintainers team will review it and add to list.

[salmanazeez786]

@salmanazeez786
Thank you for reporting this issue Please create Pull request for it's correction
you can check guide for contribution
https://devdocs.magento.com/guides/v2.3/contributor-guide/contributing.html

@shikhamis11

@UncleTioma has created the pull request - #24976

Do you still want me to create a new pull request ?

[magento-engcom-team]

Hi @salmanazeez786. Thank you for your report.
The issue has been fixed in #24976 by @UncleTioma in 2.4-develop branch
Related commit(s):

• 4c23a16eb20505a61edf317a1f6e75307aa6c05f
• acb45f60b6cc825b4c7eccc7d06f7c9065c62291

The fix will be available with the upcoming 2.4.0 release.