API for linting/analyzing the Klipper config

[chexxor]

Is your feature request related to a problem? Please describe

The Klipper config I have is spread across several files, and I'd like to have better tools to understand issues.

Describe the solution you'd like

I would like to have a linter/static analysis tool I can run against the current state of the config resulting from the parsed printer.cfg. I'd like to make those linter results available in the web front-end, as that is where I commonly do my Klipper config edits.

I'm not sure whether I'd need to add the linter to the Klippy project itself and simply use Moonraker to provide API access to it.

Describe alternatives you've considered

No response

Additional information

I've looked into updating the file editor of the Mailsail project first, but it only has access to a single file at a time in its file editor. To accomplish this feature request, the linter would need access to the parsed/compiled result of the printer.cfg file, and Moonraker is in a better position for that. If we have an API endpoint in Mailsail, we could return the linter results in a structured format to Mailsail, which can translate it into a format suitable for the Codemirror editor.