Make Configurator.FormatterFactories public

[hazzik]

I suggest to make Configurator.FormatterFactories public or add methods to add and remove factories from configuration. It can be useful if someone wants to use custom formatter which is, for example, not ready to be included to a library, etc.

[MehdiK]

Good idea. This is rather related to localisation suggestion in #105.

[MehdiK]

Some more thoughts:

• Why is FormatterFactories in Configurator but ConverterFactories and OrdinalizerFactories in their own classes? I get the Formatters are used from a few places while others are used from one extension only; but I think we should move these along with their resolution logic to Configurator too. Which leads me to:
• We need to make all factories public.

I think we should tackle this whole thing in one hit.

THoughts?

[justin-edwards]

I'd agree, adding / removing formatters, ordinalizers, and converters is definitely configuration so it makes sense to expose that all through Configurator.

It seems like the next thing to handle with these would be #218 and making the factories lazy by default. I'll see if I can spend a little time this evening and get a nice solution that'll take care of both issues one go without cluttering up Configurator too much.

[MehdiK]

Thanks @justin-edwards

[MehdiK]

Fixed in #243