When you build complex applications on Google Apps Script, you quickly run into the challenge of Routing.
Routing is the core mechanism in a web application that determines which code should be executed and what content should be displayed to the user in response to a specific request.
I've detailed the core issue and its nuances in the comments below.
Have you encountered this routing problem, and how did you solve it in your projects?
I like using Clean Architecture for projects on Google Apps Script. Clear separation by layers. This allows you to keep the project organized, scale it, and avoid sliding into monolithic chaos.
For example, in Spring Boot and NestJS, it is enough to describe the controllers, and the framework does the rest. But in Google Apps Script, there is simply no such infrastructure.
And this slows things down a bit, especially if you need to make professional decisions, not just a set of scripts.
Maksym Stoianov