add(getString): add third argument to getString for fallback message

[hkasemir]

addresses issue #145
adds a third argument to the getString function in withLocalized wrapped components to allow for definition of a fallback message in case the message id is not fount in the message context.

Additional future benefit to be including fallback string in extraction scripts.

[hkasemir]

@stasm - I was sort of wondering if there would be a way to format the fallback string, but it didn't look like there was a good place to put it in there. would that be possible, or more trouble than it's worth?

[stasm]

We'd need to parse the fallback string to be able to format it. It's possible (although not trivial), but I don't think we should do it. It would quickly teach developers that they don't need to maintain the en-US file at all :)

[stasm]

Thanks, @hkasemir, LGTM.

I was wondering if it would make sense to use a decorator instead of the third argument, but I don't have anything concrete to suggest. I think that the third argument is a good and simple way forward.

Also, what's up with add(getString) in the commit message?

[hkasemir]

oh, the commit message is following a convention I sometimes use at work that follows:

change_type(scope): commit message - if it's confusing I can edit the title

[stasm]

It was confusing to me at first :) No worries though.

[stasm]

Thanks again, @hkasemir!