You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we have modules for CDI and guice. In addition to this we could create a module for EasyDI too so that projects with this di framework can be easily created.
This should be relatively easy to be done as EasyDI needs far less boilerplate code in comparison to CDI and guice.
The text was updated successfully, but these errors were encountered:
- renamed `configureBindings` method to `initEasyDi`. This better fits the actual use cases for this method and matches the naming of the `initMvvmfx` method.
#349
I've renamed the method configureBindings to initEasyDi.
This has 3 reasons:
It better matches what this method is used for. To configure bindings is the main purpose, however it can also be used to get dependency instances that are needed in the app class. As you can't use constructor injection in the app class, this is the only possible alternative.
the term "Binding" can be missleading in the context of JavaFX app.
The method for initialization of mvvmFX is named initMvvmFX. In the Guice module the method to configure modules is named initGuiceModules. So the new naming better matches existing livecycle methods.
At the moment we have modules for CDI and guice. In addition to this we could create a module for EasyDI too so that projects with this di framework can be easily created.
This should be relatively easy to be done as EasyDI needs far less boilerplate code in comparison to CDI and guice.
The text was updated successfully, but these errors were encountered: