Following up on jupyterhub/binderhub#1017 (comment). In particular the comment about "reduce duplication".

A possible way to do that which I've seen in other projects is to add an endpoint to the backend from which the UI loads the config. We'd have an endpoint like binder.example.com/_config which returns a JSON which is then used to configure the dropdow

Currently a user can run a notebook as a "batch job" by implicitly creating a one node "transient" pipeline. (Although "transient" is technically incorrect, I am using the term to highlight the fact that the generated pipeline is hidden from the user in the Elyra UI and can only be seen (and re-used) in the Kubeflows Pipelines UI.)

![image](https://user-images.githubusercontent.com/13068832/935

Objective

Python 3.6 and above supports type hints and optional statically typing of Python code. Since its introduction is has seen a lot of adoption in many Python projects in particular in larger code bases. Type hints are completely optional and are stripped by the Python parser before runtime.

I am not the only one @plumerai anymore who li