Allows custom Currency Provider through inheritance

[tigitz]

This is a minimal proof of concept for #30 and #61

It uses inheritance as a point of extension for custom logic.

Pros are that existing userland logic will still work as expected while allowing flexibility for more complex use cases.

However extending through composition would be much more robust but would require a profound rewrite of current classes.

[BenMorel]

Interesting approach @tigitz!

It uses inheritance as a point of extension for custom logic.

Why extend Currency though, when we could just have a CurrencyInterface? (Currency should probably be renamed to ISOCurrency in this case, for consistency.)

However extending through composition would be much more robust but would require a profound rewrite of current classes.

Can you share the rough idea without writing the code?

[tigitz]

Thanks 🙂

Why extend Currency though, when we could just have a CurrencyInterface? (Currency should probably be renamed to ISOCurrency in this case, for consistency.)

You're right, this is part of the "composition" approach I'm suggesting, which would have a more significant impact. I'm in the process of writing a more detailed comment in #30 to explain everything thoroughly. Catch you there 😉

[tigitz]

Superseded by #95