jans-cli usability

[manojs1978]

please find some usability update
jans-cli_usability.pdf

[ossdhaval]

If we can add two more:

Optional fields should be sorted or categorised so that options are easy to locate. As shown in image below, optional fields presents a huge list of optional fields. If you are looking for a particular option, it is not easy to find. For example, if it was sorted in alphabetical order, it would be easy. Or may be categorised in some logical way.

Plus, the Populate optional fields? doesn't have any suggestions for input.

[ossdhaval]

captured this comment as #1349

[devrimyatar]

Categorisation not possible, I will sort them.

[ossdhaval]

Prompt for scopes optional parameter says array of string separated by _,» but the example is space separated

«Provide list of scopes granted to the client. Type: array of string separated by _,»
Example: read write dolphin

[ossdhaval]

Captured this comment as #1350

[ossdhaval]

In the end, after finishing giving all inputs, when JSON gets printed on screen, give an option to save it in place of having the user copy it manually.

[ossdhaval]

Captured this comment as #1352

[manojs1978]

what is expected behaviour if someone not press enter within 1800 sec after device verification or press enter before device verification.?

i am getting bad request (error 400) but i think it should be timeout if user not press enter within 1800 sec and when pressed enter before device verification it should not give any error till 1800 sec.

[devrimyatar]

We can count timeout, an look for the response of the server if device verification is done, if not warn user and wait until user hits enter again.

[devrimyatar]

@ossdhaval Thanks for nice suggestions. I will implement these on this branch https://github.com/JanssenProject/jans/tree/jans-cli-no-swagger-client .

[ossdhaval]

Closing this as most of the suggestions have been incorporated.