Rules do not scan dependency injection without a handler

[maschnetwork]

Problem: You can run standard Spring Boot applications via the Serverless Java Container or the Lambda Web Adapter. In that case, no specific handler interface needs to be implemented. Currently the SnapStart rules would therefore not recognize any violation of the rules:

public class UnicornControllerHandler {

    private final UnicornService unicornService;
    private final UUID uuid;
    private static final Logger logger = LoggerFactory.getLogger(UnicornControllerHandler.class);

    public UnicornControllerHandler(UnicornService unicornService) {
        this.unicornService = unicornService;
        uuid = UUID.randomUUID();
    }
}

This is somehow related to #24 but the checks seem to only apply when the class and the method have a specific name.

[tobixlea]

The checks will apply as long as the method contains the word Handler, as stated in #24. From the PR description: Solving this problem will allow us to scan most Lambda Handler classes that are currently falling through the cracks. which I believe would prevent the issue you are stating, is that what you are meaning?

The example class and method you provided in your example contains the key word Handler so the checks should correctly apply.