💡 [REQUEST] - Rich type completion for non trivial type parameters

[Oberacda]

Implementation PR

No response

Reference Issues

No response

Summary

We want custom-type classes for several options:

• ROS Types
  • Services
  • Actions
  • Msgs
  • Topic Names
• Paths
  • Subtrees (file:// and package://)
  • Filesystem Nodes (file://)

This will allow us to create better autocompletion in the Web UI

Basic Example

• The Topic Subscriber node requests a ROS Message type, but the autocompletion allows all types, including basic Python types, to be references.
• The subtree node has a pure text input for specifying the path of the subtree. A filebrowser to define this would be nice.

Drawbacks

This will require changeing all the type completion types, both in the UI and the Backend.

Unresolved questions

No response

[Oberacda]

@nspielbau you think this makes sense?

[nspielbau]

A filebrowser for subtrees sounds very helpful and good for usability.
While the type completion also sounds nice, we will need to be careful to not restrict Node Classes that want access to those primitive Python types as well as ROS interfaces e.g. GetAttr

[Oberacda]

Related to #113