should always use full_return
Is your feature request related to a problem? Please describe.
Some commands return only very simple information, like true/false. This is indistinguishable from the return of false on a timeout.
Describe the solution you'd like
The API should use full_return as much as possible. The response from that clearly indicates success/failure as well as a separate result.
Update: while the data is better separated from the meta-data, it does not indicate success/failure. instead, it provided a result-code separate from the results. but the indication for success/failure is still missing.
Update: this is only relevant for free-format commands, not for the internal commands. When internal commands fail we don't show much extra information anyway.
Update: this must be arranged as a setting saltgui_use_full_return: True (default: False) as this is a breaking change. not only will the gui show different output, also the job history as maintained by the SaltStack system will change a little bit. And that may be an unpleasant surprise for some.
retrieving setting is done TODO: use setting in many places TODO: testing
Kudos, SonarCloud Quality Gate passed! 
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
with full_return, also the JID is returned. this allows SaltGUI to jump directly to the JOB view for that
Kudos, SonarCloud Quality Gate passed! 
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication