Skip to content

Releases: go-playground/universal-translator

Release 0.18.1

30 Jan 04:28
f83cd52
Compare
Choose a tag to compare

What's new?

  • Updated deps.
  • Change to use GitHub Actions for CI.

Release 0.18.0

08 Aug 22:23
04491fe
Compare
Choose a tag to compare

What's new?

  • Updated to latest deps
  • Fixed some linting errors.

Release 0.17.0

11 Nov 20:23
f87b140
Compare
Choose a tag to compare

What's new?

  • Updated to Go Modules
  • Fixed Examples imports.

Release 0.16.0

09 Feb 16:15
Compare
Choose a tag to compare

What changed?

Backing locales package updated to CLDR v30.0.3

be sure to update you locales package with a go get -u github.com/go-playground/locales

Release 0.15.0

08 Feb 19:43
Compare
Choose a tag to compare

What's been added?

  • A file format for Import & Export has been created
  • Import & Export logic has been added.
    • Import recursively reads all files within a directory, so you may organise however you wish.
    • Export exports each locale to it's own file, with name of locale.
    • Currently only JSON is programmed in, but anyone who want to implement any other format is welcome and it's all setup to do so going forward.

More?

  • A full example with files and without files has been added showing how this would be integrated into a web application. NOTE: this is only how I would do it...but you could do it in any other way you wish.
  • File Format examples have also been added

This is for #6 and #7

Release 0.14.1

04 Feb 22:22
Compare
Choose a tag to compare

What was fixed?

  • a typo in the example code was corrected, thanks @tmc for the pull request!

Release 0.14.0

14 Sep 18:36
Compare
Choose a tag to compare

What's New?

  • Just corrected some error type's text, no breaking changes.

Release 0.13.0

11 Sep 20:34
Compare
Choose a tag to compare

What was added/changed?

  • examples updated as underlying locales package now returns string instead of []byte for convenience and safety

Release 0.12.2

08 Sep 14:06
Compare
Choose a tag to compare

What was fixed?

  • there was no way to determine of a locale was found or just used the fallback so added a found return param to GetTranslator() and FindTranslator() functions.
    • Why is that important? because if an unsupported locale is detected some people may want to redirect to a locale selection page of supported languages, store that in cookie and use that going forward.

Release 0.12.1

01 Sep 17:30
Compare
Choose a tag to compare

What was fixed?

  • corrected error with param index calculation when adding a normal translation.