-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EAP 2023.1: Do not use constructor injection #604
Comments
Thanks for the report, I'll have a look when I get a tick. |
I'll be honest, at first glance I'm lost. The docs clearly state that project services can have The only thing I can think of is if they're picking up the private constructor, which would annoy the fuck out of me, as I don't want to losen the constraints on the class even further by allowing those values to be uninitialised. In any case, it'll have to wait for a day when I have more time. |
Thanks. The fix is easy enough if they really don't want constructors, it's just a shitty architectural choice, to enforce initialisation of incomplete services 🤦 |
Hopefully fixed - I haven't run it up with the EAP due to time constraints, so that's a hopefully (especially if there are other instances). |
On the latest EAP, the IDE reports the following:
The text was updated successfully, but these errors were encountered: