This may be the most beautifully succinct service doc intro sentence I've ever written...

working on a shell library with the business logic for an Angular "white label" app workspace, and `ShellService` just got introduced as:

"this service serves to serve all other services.."

me thinks today is a good day for coding. 😎

It shall be called ServiceService

@Lensflare Please dont abbreviate it tho

Or just call it Service²

@thebiochemic oh hell no, I hate abbreviated names with a fiery passion.. IntelliSense works better with longer names anyway. (:

Yeah abbreviations were sexy when monitor space was very limited and code was printed on paper.

Jokes aside , Isn't this a facade pattern usecase ?

@sam94 hmmm, maybe a little bit, yeah.. it's primary purpose is to catch and process configuration from an injection token in its parent module, which is in turn populated through a static method that returns a module with providers, which is in turn called by the application project that is implementing the "shell app".

Basically, it's a monorepo for a "single application and it's additional flavours".. to add a new flavour, I create a new app project (with custom branding, language strings, logos, etc), and import my shell module. That's it.