New JSON Lint Not Using Tabs over Spaces when validating #104
Description
While I understand that json files work fine either with tabs or spaces, somehow tabs tends to be much more softer on the size department over the use of spaces. This caught me slightly off guard when I notice the update to the site when trying to optimize a code since it usually cleaned and converted the spaces on the start to tabs which (personally) I prefer. Unsure if that can be reverted back or if its going to stay that way.
It always used to do that when I click on validate json. Now it just doesn't even when trying the compress to validate.