Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Suggestion: improve logging in LocaleMessage

    I had a problem with a .properties i18n key in one of my datasources. (just a typo).

    Unfortunately, the logmessage from your com.isomorphic.util.LocaleMessage is just "Bad key" :)
    I set a breakpoint in your decompiled class, and i got the problematic key that way. A friendly suggestion would be to also put the actual name of the bad key in the message.

    (row 118 in decompiled localemessage; throw new MissingResourceException("Bad key", (String)null, (String)null);)

    #2
    We've replaced this with a meaningful log message, thank you for letting us know.

    Comment

    Working...
    X