editorconfig: use an indentation of 2 for json and yaml files

[GrimLink]

Summary (*)

Consider using a indentation of 2 for json and yaml files.
The recommended default for the package.json and yaml files is 2.

The only exception is composer that uses 4.

Examples (*)

None, this just a formatting suggestion

Proposed solution

See my Pr #30062

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ihor-sviziev]

Priority and Severity labels were copied from #30066 that duplicates this issue

[magento-engcom-team]

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

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

[magento-engcom-team]

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

• b70851de42e1430dc09f0ac88b4ecc8f82abc4fd
• f7f5dce0d1415661441e9c8f5ccf0b24bea30f28
• 9ef8d9ddb9dbdc185489f0fe3475aade28da167a
• 93d79b8d638568ac5a529b833cbb043333d3be0d
• 0533f2e35f4779d8b6fc14ed316c3c0e483698cb
• 5b476475ad8eb2a99db7543f2881978b9b7fbe53
• 9d8a772c4f0efeb15f4fac12e294123f27e9f81b
• 5f704dbd65b4f1cb8ca93a80d70cdbe466cf765c
• c722790487631c0ce78d753d2dfe9d97c7606a18

The fix will be available with the upcoming 2.4.2 release.