Epic Way of linting or auto-formatting

How does Epic handle linting or auto-formatting? Does it do it as a validation in SubmitTool or as an extension in the IDE?

[Attachment Removed]

Steps to Reproduce[Attachment Removed]

Hi,

We have integrated BugHawks (GitHub - steinwurf/bughawk: A tool for checking a set of source files for common bugs. · GitHub) in SubmitTools for ‘linting’. We also run various static analyzer on the build farm nightly. Regarding auto-formatting, I’m assuming you mean auto-formatting the submitted code, I’m not aware of anything. The topic came few years ago and some people suggested clang-format to auto-format the engine code, but in general, we don’t want to auto-format any existing code because it creates more difficulties to customers to integrate fixes or merge their customized engine with a newer engine. So we reformat the code carefully when needed, but we try to avoid any large reformatting. So formatting issues are responsibility of the code writer and the reviewers and it’s still manual.

Regards,

Patrick

[Attachment Removed]