Missing store_name in GraphQl Resolver

[sunel]

Preconditions (*)

1. Magento 2.3.4

Steps to reproduce (*)

1. Request for store_name in storeConfig Query

Expected result (*)

1. Return store name

{
  "data":{
       "storeConfig":{
               "root_category_id":2,
               "store_name": "Magento"
        }
}

Actual result (*)

{
  "data":{
       "storeConfig":{
               "root_category_id":2,
               "store_name": null
        }
}

As Mentioned in schema 'store_name' can be queried

magento2/app/code/Magento/StoreGraphQl/etc/schema.graphqls

Line 33 in d4a9098

store_name : String @doc(description: "Name of the store")

But in StoreConfigDataProvider.php its not resolved

magento2/app/code/Magento/StoreGraphQl/Model/Resolver/Store/StoreConfigDataProvider.php

Lines 71 to 94 in d4a9098

	private function getBaseConfigData(StoreInterface $store) : array
	{
	$storeConfig = current($this->storeConfigManager->getStoreConfigs([$store->getCode()]));
	$storeConfigData = [
	'id' => $storeConfig->getId(),
	'code' => $storeConfig->getCode(),
	'website_id' => $storeConfig->getWebsiteId(),
	'locale' => $storeConfig->getLocale(),
	'base_currency_code' => $storeConfig->getBaseCurrencyCode(),
	'default_display_currency_code' => $storeConfig->getDefaultDisplayCurrencyCode(),
	'timezone' => $storeConfig->getTimezone(),
	'weight_unit' => $storeConfig->getWeightUnit(),
	'base_url' => $storeConfig->getBaseUrl(),
	'base_link_url' => $storeConfig->getBaseLinkUrl(),
	'base_static_url' => $storeConfig->getSecureBaseStaticUrl(),
	'base_media_url' => $storeConfig->getBaseMediaUrl(),
	'secure_base_url' => $storeConfig->getSecureBaseUrl(),
	'secure_base_link_url' => $storeConfig->getSecureBaseLinkUrl(),
	'secure_base_static_url' => $storeConfig->getSecureBaseStaticUrl(),
	'secure_base_media_url' => $storeConfig->getSecureBaseMediaUrl()
	];
	return $storeConfigData;
	}

[m2-assistant]

Hi @sunel. 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.

@sunel 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.

[yogeshkarodiya]

I am working on this issue

[m2-assistant]

Hi @danielrenaud. 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.