With #475 (PR for #332) we introduced the possibility to use a new annotation @Initialize to mark a method in a viewModel so that it is invoced after injection of dependencies is done.
However, the first implementation in #475 only supports a single method with this annotation. Additionally, an existing public void initialize method was ignored when a method with the new annotation is present.
These limitations aren't useful or needed. We should support multiple initializer methods and the combination with the existing naming convention.
With #475 (PR for #332) we introduced the possibility to use a new annotation
@Initializeto mark a method in a viewModel so that it is invoced after injection of dependencies is done.However, the first implementation in #475 only supports a single method with this annotation. Additionally, an existing
public void initializemethod was ignored when a method with the new annotation is present.These limitations aren't useful or needed. We should support multiple initializer methods and the combination with the existing naming convention.