Build increased by 100% when set "NG_BUILD_MANGLE=false"

[rbernalagainagain]

In the Angular projects, the size of the build in increased more than 100% when set in the application NG_BUILD_MANGLE=false.

example: NG_BUILD_MANGLE=false.

example: NG_BUILD_MANGLE=true

I don't consider this an issue, but I don't think it's much of a sacrifice for the applications.
Angular is very restrictive with its core, and I can't find a possible solution quickly.

What possible solution can we find?

[cesalberca]

It's a pity that Angular doesn't optimize the code correctly with that option set. We use the name of the classes to handle caching so we can't have their name minificated. A workaround might be to add a way to provide custom cache keys in order to be able to optimize the code. For now I'll create an issue on Angular's repo and see if it can be fixed.

[esuca]

What if we change the implementation of our cache? I could be wrong, but maybe within the cache decorator we could define a new metadata key using reflection for each command or query.
Another workaround could be to use instanceof, but I'm not sure.

[cesalberca]

So maybe instead of extending from Query or Command we could have a decorator? The problem with that is that without extending from an abstract class forces you to implement the right method. And doing both is a little bit redundant, no?

[esuca]

If we have a decorator we need an interface to force the user to use the right method and have better typescript type inference. Also with a decorator we don't need to have the internalExecute() method... Take a look at Nestjs CQRS implementation. For example the @QueryHandler only defines the metadata, then inside the QueryBus the handler is registered using the metadata defined before.
I'm sure we could do something similar in Archimedes