> I agree to @retailcoder and @MDoerner. The inspection (and a possible fix) is independent from the export of an empty "component" where a component can also be a worksheet. While the code part of the worksheet can be "empty" the other parts of the worksheet _can_ data data and thus it shouldn't be removed by a fix.

I think the best option, if "empty" components should be exported or not, would be to add a checkbox somewhere in the settings. Then the user can decide what he/she prefers.

> Because I don't have clue about C# unfortunately I don't understand _anything_ what is coded in [EmptyModuleInspection.cs](https://github.com/rubberduck-vba/Rubberduck/blob/next/Rubberduck.CodeAnalysis/Inspections/Concrete/EmptyModuleInspection.cs).

So the only thing I came up with is, is to add something like

```csharp
// BUG: not sure how to get the text of the component. The `text` part is a guess.
// TODO: Remove the "invisible header" (for components other than DOCCLS)
string com

Merge pull request #6059 from Mo-Gul/next

harmonize indention of empty lines in `TestCodeGenerator`