The current implementation of the wizard form involves multiple components that handle the logic of different use-case groups. This leads to an excessive number of components and complicates the codebase. To simplify and streamline the implementation, we propose extending the wizard form by using a single component to handle the logic of a given use-case group. This way, we can declare the fields to use for every specific use-case and then render those fields. The fields to render will be stored in a common list, and this list will be updated dynamically depending on the selected use-case.
Motivation
The motivation behind implementing a single component-based wizard form is to reduce code complexity, enhance maintainability, and improve developer productivity. With the current implementation, adding or modifying a use-case requires substantial rework, as it involves multiple components. By introducing a single component that can handle multiple use-cases, we can significantly reduce the number of components and simplify the overall architecture. This will make it easier for developers to understand and extend the wizard form functionality.
Description
The current implementation of the wizard form involves multiple components that handle the logic of different use-case groups. This leads to an excessive number of components and complicates the codebase. To simplify and streamline the implementation, we propose extending the wizard form by using a single component to handle the logic of a given use-case group. This way, we can declare the fields to use for every specific use-case and then render those fields. The fields to render will be stored in a common list, and this list will be updated dynamically depending on the selected use-case.
Motivation
The motivation behind implementing a single component-based wizard form is to reduce code complexity, enhance maintainability, and improve developer productivity. With the current implementation, adding or modifying a use-case requires substantial rework, as it involves multiple components. By introducing a single component that can handle multiple use-cases, we can significantly reduce the number of components and simplify the overall architecture. This will make it easier for developers to understand and extend the wizard form functionality.