Subgraph inputs do not expose editable fields

[fnf]

Thank you for implementing the subgraph feature. Its usability is massive compared to group nodes.

A feature that I sorely missed from Group Node though: is that the input fields would be rendered like normal instead of condensed to a single input socket. It prevents changing the settings of those input fields unless user either:

1. Enters the subgraph and change them, or
2. Create a new input field with the same type and connect it to the input socket of the subgraph

1. is not ideal for nested subgraph and quick iterations and 2) will clutter the workflow again i.e., it makes the subgraph feature less useful. 2) also has a problem that only a very limited amount of input types are re-creatable: it doesn't work with things like Combo boxes.

Could anyone let me know if this is a planned feature?.

[fnf]

As a hack, I tried adding the Group Node feature back but realised that #3905 also removed the ability to execute Group Node altogether.

The idea is that I'd use subgraph to build reusable elements together with Group Node that still exposes the input as editable fields.

[fnf]

Looks like it was raised here #4189 .