Currently, StreamFlow requires the definition of a framework.yml file to register new components in the framework.
It would allow for much quicker development to also include the ability to define the component settings such as the name/label/description at the class level using custom annotations. In addition, properties could also be annotated used field annotations on the properties directly.
If possible, it would be good to support the annotation approach AND the framework.yml approach in case user's have a specific preference or are working with legacy code.
Currently, StreamFlow requires the definition of a framework.yml file to register new components in the framework.
It would allow for much quicker development to also include the ability to define the component settings such as the name/label/description at the class level using custom annotations. In addition, properties could also be annotated used field annotations on the properties directly.
If possible, it would be good to support the annotation approach AND the framework.yml approach in case user's have a specific preference or are working with legacy code.