Suppress Initialization Check for fields initialized with a Constructor Injection

[gabizou]

In the cases where we have Mixins writing new fields, we could do traditional field initialization here, but it would be nice to tell IntelliJ to stop being stubborn learn to tell additional constructor called methods to initialize fields.

This could be tricky as constructor injection can be tricky, but I'm fairly sure this sort of injection will always work, even with multiple constructors without a no-args constructor, right @Mumfrey ?

[DenWav]

I don't know Mixins well enough to say with confidence. If that's injecting into {} then it will be called regardless of the constructor. But I assume you can give a signature to <init>, so I'm not sure how that would work.

[gabizou]

Since the injection in the screenshot is injecting to <init>* would inject into every constructor found, but <init> would inject into the no-args constructor, if there is one.

Granted, could ask @Mumfrey for clarification, but for the moment, I've changed this to direct field assignment instead of injecting.

[Mumfrey]

No, <init> alone would inject into the first ctor.

[DenWav]

The injection in the screenshot is injecting into <init> too, not <init>*.