BUG: Category Repository get()'s argument store_id does not work

[lbajsarowicz]

Description

The implementation of $storeId support was never finished.

Preconditions (*)

1. Magento 2.4-develop

Steps to reproduce (*)

1. Create 2 stores
2. default with ID 1
3. extra with ID 2
4. Create Category with url_key value: category-1 (let's assume it's ID is 333)
5. Open Category edit and change scope to extra store
6. Change url_key to value some-magic-key
7. Create class that use CategoryRepositoryInterface
8. Execute $categoryRepository->get(333, 2)

Data is properly saved in the MySQL table:

Expected result (*)

1. Category data with url_key = some-magic-key is returned

Actual result (*)

1. Category data with url_key = category-1 is returned

Related issues

1. https://github.com/magento/magento2#12881

Not related issues

1. Please not treat it as related to Saving product with non-default store scope causes untouched attributes to become store scoped if loaded using ProductRepository #8897: That one is related with EAV error on saving attributes when saved with API.

[m2-assistant]

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

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

[vincentle89]

Hi @lbajsarowicz

I can't reproduce this issue on version 2.4-develop. Please take a look at my record: https://youtu.be/oVCcF9Av06E

[lbajsarowicz]

Let me verify that, as I also covered that with integration test and... Isolated, that problem does not occur.

[lbajsarowicz]

Problem is actually related to internal cache storage.
It's not related to Repository but to the fact, that it does not update cache after save.

[magento-engcom-team]

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

• 2d15e9107418f04626ef021451774cdc438f1b42
• 8ad33f504b11976a4faa53c9024767a740e6bc44

The fix will be available with the upcoming 2.4.0 release.