New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added optional creation of Lang obect is one if correct. #338
Conversation
👍 actually my logs are filled by stacktraces because of clients using invalid acceptLanguage headers |
same here - what is still needed to make this pullable? |
Hi there, could you please sign our CLA? http://typesafe.com/contribute/cla |
Done // rssh: mobile ----- Reply message ----- Hi there, could you please sign our CLA? http://typesafe.com/contribute/cla Reply to this email directly or view it on GitHub: |
This is a critical problem for many people. Thanks. |
actually, just one small thing, could you please rename the option method to get? Otherwise it looks good. Thanks |
Thanks. This is now merged, please provide a corresponding ticket* (lighthouse: https://play.lighthouseapp.com/projects/82401-play-20/milestones/137248-21) and a functional test next time ( as described here: https://github.com/playframework/Play20/wiki/Guidelines) Thanks again! (* I have created a ticket for this pull request already) |
I am still getting this with 2.1-TRUNK from today (2012-06-27): java.lang.RuntimeException: Unrecognized language: * |
I really hate this bug, please fix it. It's getting in the way of testing. |
It would be good to have in API ability to create language from string only if string can represent correct language. This is needed when you want to have explicit localization be available (for example when language is set as part or url). So, I added
optional
method to Lang object, with typical usage: