Multi-store: Missing store codes in relation to a group and website

[magento-engcom-team]

In order to switch stores in a Multi-store Magento instance, a developer would need a GraphQL Query that would return a list with the following data (currently available for the current store inside storeConfig)

 

query {
  storeConfig {
1. Available
    id 
    header*logo*src 
    logo_alt 
    logo_width 
    logo_height 
    store_name
    ...

1. Missing
    stores {
       id 
       header*logo*src 
       logo_alt 
       logo_width 
       logo_height 
       store_name
       ...
    }
 
  }
}

 

!image-2020-05-11-10-11-04-038.png!

Requirements:

1. This should be implemented in accordance with architectural proposal Add query to get available stores architecture#390
2. availableStores query should only return other stores under the same website as the current store. It should not expose other websites.

 

[m2-assistant]

Hi @magento-engcom-team. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

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

[m2-assistant]

Hi @gallyamov. 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.4-develop branch
     Details

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

---

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

[magento-engcom-team]

❌ Something went wrong. Cannot update Jira issue (https://jira.corp.magento.com/browse/MC-34187).

[magento-engcom-team]

❌ Something went wrong. Cannot update Jira issue (https://jira.corp.magento.com/browse/MC-34187).

[magento-engcom-team]

❌ Something went wrong. Cannot update Jira issue (https://jira.corp.magento.com/browse/MC-34187).

[magento-engcom-team]

❌ Something went wrong. Cannot update Jira issue (https://jira.corp.magento.com/browse/MC-34187).

[magento-engcom-team]

❌ Something went wrong. Cannot update Jira issue (https://jira.corp.magento.com/browse/MC-34187).