Avoid module implementation minification

Question

Avoid module implementation minification

LukasPaczos opened this issue 5 years ago · 5 comments

Currently, the module implementation classes that skip configuration can be minified because they are stored only as raw strings and later looked up via reflection. We should look into a way of storing the full class reference to avoid those issues and possibly improve performance.

/cc @RingerJK @Guardiola31337

Answer 1 · 2020-03-26T15:20:22.000Z

X_ModuleConfiguration class has whole path and name of class and that's info that require for proguard. We need a way to provide rules to customer and internal minifying, right? I'd like to get that we on the same line 😄

Answer 2 · 2020-03-26T15:46:55.000Z

That would be one option, another would be to actually import the class instead of storing the values in string constants.

Answer 3 · 2020-03-30T11:20:10.000Z

That would be one option, another would be to actually import the class instead of storing the values in string constants.

@LukasPaczos I think it won't work because Configurable modules are added as runtimeOnly and they aren't available on compile time

Answer 4 · 2020-03-30T11:24:22.000Z

This is true for the dependency, but the generated configuration class should have direct access to the implementation as long as it's public, which could allow us to link the class itself.

Answer 5 · 2020-04-03T13:27:07.000Z

Thanks to #32 we have no issues referencing the class, but the minified code still fails.