Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Иван Бишевац
@biske
Hi guys, I'm using Globalize to store translations in different languages.
But I'm not sure why Globalize stores language as locale.
Language should be :en, :ru, :ch, etc.
But locale should be :en_US, :en_GB, :ru_RU, etc.
Does Globalize has support for locales or only for languages?
Philip Arndt
@parndt
locales
Tim Schmelmer
@timbogit
Hello globalize folks! Any chance that we will soon have a Rails 5.2 compliant version of the globalize/globalize gem out there on Rubygems?
I see that @dalpo merged in a PR that enables it ~ 3 weeks back.
Will there be a new (minor?) release of the gems soon?
Tim Schmelmer
@timbogit
Any updates / thoughts, @parndt or @dalpo ?
Philip Arndt
@parndt
@timbogit sure, I'll release (funnily enough) version 5.2.0 with the latest code in master
Tim Schmelmer
@timbogit
Awesome! I saw the test suite having errors' though. Is that cause for concern with the new gem version?
Philip Arndt
@parndt
yeah..... I just noticed that..
so that'll be why there's no version
booo
Tim Schmelmer
@timbogit
:-(
Philip Arndt
@parndt
Sorry, I've very little time for open source lately
Tim Schmelmer
@timbogit
yeah, thanks for all the time you can put in
Philip Arndt
@parndt
❤️
seems it's all related to dirty tracking
Tim Schmelmer
@timbogit
yup
Philip Arndt
@parndt
globalize/globalize#672
often these things can get fixed just by merging PRs ;)
the community is so lovely
Tim Schmelmer
@timbogit
:heartpulse:
Philip Arndt
@parndt
what are you using globalize for @timbogit ?
Tim Schmelmer
@timbogit
We are using it in a couple of rails apps (via an engine that is shared between them) to localize web content
Philip Arndt
@parndt
have you seen https://github.com/shioyama/mobility/ by @shioyama ?
Tim Schmelmer
@timbogit
Right now, we'd really like to upgrade to Rails 5.2+, and it seems that globalize is our only gem that keeps us on Rails 5.0 or .1
Philip Arndt
@parndt
yeah, there are two failing tests that prevent me recommending you just use the master branch of globalize
Tim Schmelmer
@timbogit
I have heard about the gem, but we haven't really evaluated it (and what it would take in our codebase to switch to it)
Philip Arndt
@parndt
it's what globalize should be - sometimes I think that we should just deprecate globalize and point people to mobility
Tim Schmelmer
@timbogit
@parndt are you saying the PR above doesn't address the root cause for the test failures?
Philip Arndt
@parndt
yeah it fixed two issues
but alas still the build fails
Tim Schmelmer
@timbogit
:panda_face:
Philip Arndt
@parndt
I feel like maybe I made it worse :D
ah no I had 6 failures locally before too
Chris Salzberg
@shioyama

@parndt thanks for your flattering comment :smile:

@timbogit FWIW: https://github.com/shioyama/mobility/wiki/Migrating-from-Globalize

There are a couple small things with querying which are not yet supported, and some small differences, everything should be documented there in the wiki.
Chris Salzberg
@shioyama
My issue with Globalize is that it goes too far monkey-patching, which leads to strange, hard-to-debug issues, especially when upgrading Rails. And since it's "all or nothing", you can't (say) disable dirty-tracking if you don't need it. This makes it hard to offer a new version until all compatibility issues are completely resolved.
I'm partly responsible for that since I wrote some of that monkey-patching code... :worried:
But once it's there, nobody wants to remove it.
Tim Schmelmer
@timbogit
Wow, thanks for the awesome docs for migrating, @shioyama ! We will definitely check this out!
Chris Salzberg
@shioyama
Great, and let me know if you notice anything missing.
Philip Arndt
@parndt
Those are my issues with Globalize too :wink:
part of me wonders if we can't just add a shallow layer on top of Mobility and retain all existing globalize functionality that way
Chris Salzberg
@shioyama
Maybe in a separate gem or something
But the problem is that what people now expect Globalize to do is a problem
Philip Arndt
@parndt
people can always stay on the current version :)
edzyo
@edzyo
Hello, If i create query(Post.all - for example) can i exclude object if it havent translation in one of the translation language
Matthew Kennedy
@MatthewKennedy
Rails 5.2 any progress?