Is your feature request related to a problem? Please describe. Currently, notebooks only support rendering text fields based on parsed environment variables. Also, KFP pipeline components only support rudimentary parameter descriptions (e.g. type)
This way a complex component like a DL model can't be properly parameterized - especially if parameter visibility is dependent on the choice of other parameters (e.g. kernel type is only a valid option if kernalized regression is chosen)
Describe the solution you'd like Please have a look at this "galaxy tool" - a galaxy tool is a component for the galaxy pipeline tool. In this part of the XML the actual behavior of the property editing UI is expressed (including UI components only visible under certain circumstances)
I'd like to see something similar for Elyra. The configuration could be included in a cell in the notebook so that a citizen data scientist can edit it as well
Either the XML can be used 1:1 or an equivalent can be used. If should be evaluated if the code base from Galaxy could be used (either by proposing the Galaxy team to externalize this functionality so that it becomes a dependency for Galaxy and Elyra) or just copying the code.
Describe alternatives you've considered There are not alternatives
Additional context Example of the component configuration dialog in galaxy