Hi Ilya, Thanks for the python usage example.
AWS cli does not support interactive mode at all. Google too. Even Google Big query cli [1] executes sql queries without interactive shell. For REPL-first tools like Reql [2], ksqlDB CLI [3], or SnowSQL [4] it is common thing to enter the REPL if command was executed without any arguments. CLIs that do not support the REPL (or REPL is not the main value of those tools) tend to print help on empty arguments. [1] https://cloud.google.com/bigquery/docs/bq-command-line-tool <https://cloud.google.com/bigquery/docs/bq-command-line-tool> [2] https://github.com/Workshape/reql-cli <https://github.com/Workshape/reql-cli> [3] https://docs.ksqldb.io/en/latest/operate-and-deploy/installation/cli-config/ <https://docs.ksqldb.io/en/latest/operate-and-deploy/installation/cli-config/> [4] https://docs.snowflake.com/en/user-guide/snowsql-use.html <https://docs.snowflake.com/en/user-guide/snowsql-use.html> > On 19 May 2022, at 11:44, Ilya Korol <llivezk...@gmail.com> wrote: > > From my perspective we should move towards existing UX approaches. For > example: > python - enters shell > python --help - prints help > python -c - executes command > > What about other CLI tools that works with remote services? I can't remember > properly but do AWS, openshift or maybe GCP CLIs also supports shell mode? If > so, how it is organized? > > 19.05.2022 17:53, Aleksandr Pakhomov пишет: >> I got it. What do you think about this proposal: >> >> - “ignite” prints help >> - “ignite shell” enters REPL >> >> Or >> >> - “ignite” prints help >> - “ignite-shell” enters REPL and it is a separate application >> >> I prefer the first varian but I would like to hear opinions of other >> community members. >> >> >>> On 19 May 2022, at 01:16, Andrey Gura <ag...@apache.org> wrote: >>> >>> I can just have a mistake in my script, e.g. running ignite command >>> without any parameters. What will happen in such a case from the >>> script perspective? I think the script will wait for returning value >>> while the shell will wait for a user input. Due to a server-side >>> nature of the script it will hang forever because there is no user on >>> the server side. >>
