Andy Damevin

For this we would need two new pickers `MavenSettingsPicker` and `NodeJSSettingsPicker` The idea is to activate them manually in the `BackendHub` depending on the selected runtime (and having a client...

We won't wait for fabric8-launcher/launcher-ui-components#903

@quintesse I guess this should be a backend feature then.

There may be a frontend one soon, to filter from the url, but that's another use case it seems..

@quintesse because we requesting those runtimes from the backend having an environment for this in the frontend would be really weird IMO. For example if you add of remove a...

btw I don't think we will do url filtering per say. It will be more a way to have the interface with a fixed runtime (which can only be done...

> @ia3andy when you say "I don't think we will do url filtering per say", do you already have an idea of how you'd do it? @quintesse yes having a...

> @ia3andy Quarkus is not the only use-case. The runtime teams have been asking for ages to have an option where they can send users to https://developers.redhat.com/launch/login where they will...

@gastaldi yes I agree. Regarding the frontend, I see it a bit differently, filtering isn't really needed because there is not a lot of runtimes. Here is what I have...

So I see two features for the frontend: 1. ability to preselect some configuration for the new app in the url (runtime, capabilities, ...) 2. ability to define a reduce...