Skip to content
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.

Sign up for GitHub

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

Jump to bottom

better i18n Accept-Language parsing to properly support examples (+ as standalone function) #1850

Merged
merged 3 commits into from
Jul 18, 2017
Merged

better i18n Accept-Language parsing to properly support examples (+ as standalone function) #1850

merged 3 commits into from
Jul 18, 2017

Commits on Jul 18, 2017

  1. More flexible standalone parsing of Accept-Language 

    there is now a function to replicate the default behaviour of a translation context (as returning null simply uses the first element in languages) + the cases that were advertised in the examples (like rewriting en_GB to en_US if only that is available) actually work now and are unittested.
Validation for checking if there are ambigious languages in the allowed languages is still not implemented, but documented how it should be done to avoid issues.
    @WebFreak001
    WebFreak001 committed Jul 18, 2017
    Configuration menu
    Copy the full SHA
    2c667b4 View commit details
    Browse the repository at this point in the history

  2. Adhere to codestyle

    @WebFreak001
    WebFreak001 committed Jul 18, 2017
    Configuration menu
    Copy the full SHA
    15b7c65 View commit details
    Browse the repository at this point in the history

  3. Use std.range.only & more unittests

    @WebFreak001
    WebFreak001 committed Jul 18, 2017
    Configuration menu
    Copy the full SHA
    f3be492 View commit details
    Browse the repository at this point in the history