## Description This PR adds the spotless formatter and validator for the JSON files present in the project. If there is any invalid JSON file, the formatter fails and logs the file and the error LOC to be fixed. Since Spotless is already added to the pre-commit hook it also makes it necessary to fix the JSON and then commit the changes. Screenshot of the errors displayed for Invalid JSONs  ### Why is this Important? All of our datasource forms appear on the UI from the JSON configuration files in the plugins. If an Invalid JSON is added, it can break the datasource usage experience for the users. One such instance happened in the past, where due to a JSON formatting error, the users could not use Smart Substitution feature on production. [Reference](https://theappsmith.slack.com/archives/C040LHZN03V/p1721124893238579) Fixes #34969 ## Automation /ok-to-test tags="@tag.Sanity" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/10243164292> > Commit: 08bc87acd2e44c4a2677d3eed1bad002f991050a > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=10243164292&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Sanity` > Spec: > <hr>Mon, 05 Aug 2024 05:50:07 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||