feat: Add more explanation about `-r` and `-o` argh

[cyberboh]

Feature description

I type in terminal:

java -jar morphe-cli-1.8.0-dev.9-all.jar patch

It shows all the commands, but I still don’t understand the explanations for some of them.

-o, --out=<outputFilePath>
Path to save the patched APK file to. Defaults to the same path as the supplied APK file.

-r, --result-file=<patchingResultOutputFilePath>
Path to save the patching result file to

As far as I understand, the result file is the patched app output, is that correct, or am I misunderstanding?

Motivation

Make each command explanation clearer for beginners like me. It would also make the CLI easier to use if all explanations were written correctly.

Acknowledgements

• I have checked all open and closed feature requests and this is not a duplicate.
• I have chosen an appropriate title.

[prateek-who]

A documentation update is already in the works. See if this version of the documentation looks good to you:
https://github.com/prateek-who/morphe-cli/blob/documentation-update/docs/documentation.md

Please give your feedback on this

[cyberboh]

Morphe Desktop jar file (morphe-desktop-*-all.jar). But when I open the link, it is written as morphe-cli-1.7.0-all.jar not morphe-desktop-1.7.0-all.jar , change desktop to cli intead just to make sure end users is not confused, or change to desktop instead of cli, up-to-you.

For -r and -o abve I can make conclusion, that is -r is to store JSON file after patching, and -o is to store patched app. All good enough, Thank you.

[cyberboh]

Also, for this argh --verify-with-sdk , what is specific tools are used? Inside Sdk folders contains many sub-folders? Do you have a clue for it? I mean which folder is used to verify app?

[wchill]

--verify-with-sdk requires you have the Android SDK installed. If you have it installed, CLI will attempt to find it in the default install locations.

[cyberboh]

--verify-with-sdk requires you have the Android SDK installed. If you have it installed, CLI will attempt to find it in the default install locations.

But I still getting error #140

[kitadai31]

I think the patching result file can be called "patching result report".

This clarifies the distinction between -r and -o.
Furthermore, since the "result" in a patching process should be the patched APK file, it is appropriate to give the result JSON file a different name.
Therefore, I suggest a new name "patching result report" for it.

The description will be Path to save the patching result report file to.