innoave / soda Goto Github PK

Lets assume we want to localize a sequence of a case class or case object. For example write something like

case class Player(val name: String)
val players = List(Player("Frank"), Player("Paul"), Player("Susan"), Player("Alice))
render(players).asLocalText

render(players) is currently not supported.

It should be easy to add support for sequences.
Think of implement support for sequences in a more generic way, such as using Traversable.

Currently a message can be specified to have up to 3 dynamic arguments.
More than 3 arguments shall be supported.

Some research is needed, what would be a reasonable maximum for message arguments. How many arguments are needed by real world applications.

Currently only a view locales are statically definied, e.g. EN, EN_GB, DE, DE_AT, ...
More static definitions of locals for most used languages should be added.

Extract an API - something like RenderMessage or MessageBundle - to support different implementations for rendering localized messages.

Currently the implementation based on the java.util.ResourceBundle and java.text.MessageFormat is tightly coupled to the API and does not allow different implementations.

The methods #renderLocalized in trait RenderLocalized are recursive but not tail recursive.
This should'nt be that big problem due to the dept of cascaded case classes is not expected to be any big number. Anyway it would be cool to make this functions tail recursive.