[Issue] Adjust .editorconfig to correct the automatic formatting of db_schema_whitelist.json files

[m2-assistant]

This issue is automatically created based on existing pull request: #31166: Adjust .editorconfig to correct the automatic formatting of db_schema_whitelist.json files

---

Since the .editorconfig file was changed to use two spaces for json files, this leads to problems with db_schema_whitelist.json files. All schemas are generated by the cli setup:db-declaration:generate-whitelist command and put json content formatted by the json_decode function with JSON_PRETTY_PRINT constant. This mechanism displays an indent of 4 spaces and does not add a new line at the bottom of the file. But when we change our file db_schema.xml and run setup:db-declaration:generate-whitelist cli command, it updates the contents of the db_schema_whitelist.json file, and when we opened it in the IDE, the .editorconfig add a new line at the bottom and we can't delete it, because it is always adding at the end on saving the file.

Preconditions

Magento 2.4-develop

Related Pull Requests

#30062

Steps to reproduce

1. Open any db_schema_whitelist.json file in PhpStorm
2. And run Reformat Code
3. Press Ctrl+S to save file

Actual result

The code has been refactored and a new line added at the end

Expected result

The code is not formatted. A "No lines changed, content is properly formated" message appears

"No lines changed, content is properly formated"

[magento-engcom-team]

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

Issue Available: @engcom-Bravo, 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 @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #31166 by @DmitryFurs in 2.4-develop branch
Related commit(s):

• 59194579798bf462a46adbd8eefc8ba9804bdfe4

The fix will be available with the upcoming 2.4.3 release.