By default spell check code flags spelling problems as "Informational" level, which qualifies as a "problem" to VSCode. When legacy code is being imported, the many likely spelling issues can obscure the real code problems, so we change the reporting level to "hint" in the template repo. However, that means it is difficult to find all of the spelling issues in the workspace since they are not reported when the file in not open in an editor. It would be nice to have a Gradle task that toggles the reporting level between information and hint.
By default spell check code flags spelling problems as "Informational" level, which qualifies as a "problem" to VSCode. When legacy code is being imported, the many likely spelling issues can obscure the real code problems, so we change the reporting level to "hint" in the template repo. However, that means it is difficult to find all of the spelling issues in the workspace since they are not reported when the file in not open in an editor. It would be nice to have a Gradle task that toggles the reporting level between information and hint.