Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
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?
mariaae
@mariaae
Hi everyone! Does someone know if globalize supports postgres jsonb data type? Or should I better try the json_translate alternative? Any input is appreciated :)
Scott ♛
@sc0ttman_twitter
Hello, I was hoping that someone would be able to help me with something. I have a fairly large production database (1.5M records). I tried using the Model.create_translation_table with {migrate_data: true, remove_source_columns: false}, but it seemed to run all night and then eventually crashed. Luckily no harm was done. However, now I want to run the migration with migrate_data: false, and just run my own rake task to migrate the data. The PROBLEM is that now I dont seem to have any access to the original data attributes. I wrote a task that borrows heavily from you #move_data_to_translation_table method, however I seem to end up with nil values. The problem seems to be that record.read_attribute(attribute_name, {:translated => false}) always returns nil. Even in the console this value is nil. But for some reason in the migration the values are not nil. Can anyone let me know how I can access my original data columns for my translated values? I know the data is still in the database, I just don't know how to access it. Thanks for reading.
Tiago Santos
@santostiago
Hi
mmm, ok, this is dead
KIKUS
@imkikus_gitlab
Hi
I have a quick question
Is anyone out there?
KIKUS
@imkikus_gitlab
What is the necessary of putting gem 'activemodel-serializers-xml' in the Gemfile along with the link to globalize gem?
As per the documentation mentioned in the github