The current solution runs conduct info to resolve the current bundle names of the running ConductR cluster. If no ConductR cluster is running then the exception if catched and an empty String is returned, meaning no auto completion is available. What is not so nice is that the conduct info command is executed every time the user hits the tab key when using the conduct command, i.e. conduct info is executed for conduct run as well as for conduct load, conduct --help and so on. This slows down the auto completion at about 0.5 seconds for the commands which are not interested in the bundle names.
@huntc: I couldn't find a better scope to execute conduct info. Do you have an idea how to improve this?
huntc
commented
8 years ago
For the following commands the available bundle names in the ConductR cluster are resolved and auto completed if the user presses the tab key:
Fixes https://github.com/sbt/sbt-conductr/issues/43
The current solution runs
conduct infoto resolve the current bundle names of the running ConductR cluster. If no ConductR cluster is running then the exception if catched and an empty String is returned, meaning no auto completion is available. What is not so nice is that theconduct infocommand is executed every time the user hits the tab key when using theconductcommand, i.e.conduct infois executed forconduct runas well as forconduct load,conduct --helpand so on. This slows down the auto completion at about 0.5 seconds for the commands which are not interested in the bundle names.@huntc: I couldn't find a better scope to execute conduct info. Do you have an idea how to improve this?