Extend command line interface to match graphical user interface about briefcase HOT 4 CLOSED

@shivam-tripathi This is a great first start!

• I think having some action flag would be a good idea. I think I'd have --action {pull,push,export} or something along those lines.
• I think p for password is pretty good. What's your concern? You want to use it for pull?
• Agreed that we might want to export other formats, so having an export type would be pretty nice. Please open an issue for this!
• The ability to export a date range is something that's in the CLI but not in the GUI. Can you please open an issue for this too?

from briefcase.

I would like to work on this.

from briefcase.

@shivam-tripathi As a first step, can you please draft up a quick proposal listing what exists in the CLI and what needs to be added from the UI? For each addition, detail the flags you expect to use.

from briefcase.

Presently, there is no specific option to specify if the operation intended is "Export" or any other. Push is one of the basic operation, apart from Pull and Export.
For Pull operation, only a single flag would be needed apart from the ones already present to specify that the operation intended is pulling. Same goes for extraction. Perhaps something like "-pull" and "-e" would serve the purpose.
Another thing to be considered here is the possible change in assigned flags. Does the "p" flag is best assigned to password option?
Also, another thing I noticed is the argument name assigned to flag "f" is "name.csv". In future we might be supporting more options than just csv for export. Maybe we should change the name. ShalI open an issue for this?
In short, the code needs some restructuring - making separate modules for export and pull which would be triggered on presence of some flags signifying the request of the operation.

from briefcase.