Utilizing Google Script, I have developed various programs and mastered the use of its debugger.
Currently, my focus is on creating my first Google Drive App. The typical operation flow involves users selecting files in Google Drive, initiating a call to my App, passing selected files as State Parameters, executing doGet() to create/open Client's HTML, users choosing options in the HTML interface and submitting, followed by server-side processing of the submitted form.
Debugging a Drive App presents unique challenges compared to traditional Web Apps and Container-bounded Apps, primarily due to the presence of "State Parameters." This requires me to publish the Drive App before debugging the Client's HTML & JScript using the Javascript console and the Server's GScript through the Google Script Editor separately. Is this standard practice in Web programming? Have I overlooked any steps? Can I simulate the "State Parameter" for testing purposes to avoid debugging post-publishing (even with a test link)?
N.B. Given the clear explanation of the workflow above, I refrained from including demo code in this context.