Ok, I've just seen that you already used this in the rate limit component 😉
So just ignore what I wrote in the second paragraph 😉 Dominik -----Original Message----- From: Dominik Riemer <[email protected]> Sent: Sunday, May 31, 2020 11:19 PM To: [email protected] Subject: RE: Migrating the pipeline editor to Angular Hi Grainier, yes, that would be nice to have and one of the things that will be easier to implement after migration. I created a JIRA for tracking ideas for that kind of improvements, feel free to add more if you have any ideas! https://issues.apache.org/jira/browse/STREAMPIPES-150 There is currently a feature to create simple conditional fields called AlternativeStaticProperty: https://github.com/apache/incubator-streampipes-examples/blob/dev/streampipes-pipeline-elements-examples-processors-jvm/src/main/java/org/apache/streampipes/pe/examples/jvm/staticproperty/StaticPropertyAlternativesController.java However, the API is currently quite verbose and I'd also like to simplify this. Dominik -----Original Message----- From: Grainier Perera <[email protected]> Sent: Thursday, May 28, 2020 4:16 PM To: [email protected] Subject: Re: Migrating the pipeline editor to Angular Hi Dominik, This is awesome. Also, I'd like to see some optional fields and conditional fields (i.e different input fields depending on a toggle) with user inputs to PEs. I don't know whether this is the correct thread to ask, but I feel like it's nice to have. Grainier Perera. On Wed, 27 May 2020 at 22:46, Dominik Riemer <[email protected]> wrote: > Hi all, > > > > I’ve created an issue [1] to migrate the pipeline editor module in the > UI from AngularJS to Angular. > > > > A little background: > > We are currently running AngularJS and Angular in parallel and have > started to migrate old AngularJS modules component-by-component. The > only modules left that are still implemented in AngularJS are the > pipeline editor, the pipeline overview and the pipeline element > installation modules. I’d personally prefer to abandon AngularJS > sooner than later as it complicates the development of some UI-wide > features (e.g., better user and access management) and hinders reuse > of components. So I think I will start migrating the pipeline editor > now and maybe we can get this finished before the next release. > > > > So as this implies a rather major refactoring anyways, I’m interested > if you see any things in the UI of the pipeline editor that could be > improved or things you are missing? > > Any thoughts and ideas are welcome 😊 > > > > Dominik > > > > [1] https://issues.apache.org/jira/browse/STREAMPIPES-145 > >
