fix - loadModule reinitializes modules if the module has already been…

[nusphere]

Q	A
Bugfix	yes

Description

As descripted in #32 . there is an bug when loading a module with another loading name. there are currently 3 ways to load the same module via the module manager. the following options are available:

• namespace (legacy way)
• direct class string of the module class
• an array with "free name (string)" (key) and a module class object (value)

if you use method 1 (namespace) and method 2 (class string) for the same module in an application, it will be loaded twice and reset the previous settings.

this pull request fixes the false behavior and prevents a module from being loaded twice.

fixes #32

[nusphere]

any review possible?

[froschdesign]

@Xerkus Can you look at this? Is the module manager still relevant at all? Thanks in advance! 👍

[steffendietz]

Hi. Is there anything holding this fix back?

The target branch of this MR probably needs to be adjusted, given that 2 minor releases were published since this MR was opened.

[nusphere]

@froschdesign - ping