Public methods really needed? about interop-config

[sandrokeil]

The methods of ConfigurableInterface can be injected via constructor but how to enuse access to the properties? Put the properties module, scope and name to AbstractConfigurableFactory?

[fntlnz]

Since nothing but AbstractConfigurableFactory is supposed to implement theConfigurableInterface if not indirectly by extending the mentioned abstract factory I don't see any reason for which that Configurable interface have to actually exist.

IMHO You can just declare the missing methods as abstract and you're done.

After all, interfaces are just abstract classes that can't implement methods. And in languages like PHP this concept actually exists just because we don't have multiple inheritance and we nedeed a way to respect multiple contracts without the use of the extends keyword that can be used only once.

[sandrokeil]

@fntlnz Yes, abstract methods should be the best choice to remove 'ConfigureInterface' and the 'MandatoryOptionsInterface' could be useful. Thank you for your feedback.

[fntlnz]

Ok, now is definitely better 🎉

[sandrokeil]

I close this issue now, because I think the MandatoryOptionsInterface::getMandatoryOptions() should still be public. Thank you @fntlnz for your suggestions.