lokalise_rails:import fails in v4.0.0 about lokalise_rails HOT 5 CLOSED

Yeah, unfortunately it seems to be the case. I'm sorry for this! Here's a quick solution:

class Array
  def filter(&block)
    self.select(&block)
  end
end

This will serve as polyfill for the filter method (select should be available in 2.5).

from lokalise_rails.

I've published lokalise_manager v2.2.1 which is used by lokalise_rails v4 and fixed that issue bodrovis/lokalise_manager@9fc47fb Just to be on a safe side, you can manually include it into your Gemfile:

lokalise_rails, '~> 4'
lokalise_manager, '2.2.1'

from lokalise_rails.

Weeeell, yeah. Formally, this gem had Ruby 2.5 specified as a supported platform but actually I'm pretty sure it was a mistake from my side as it was never tested with that version, at least starting from v3. Ruby 2.5 was abandoned quite some time ago and I really don't have any plans to backport this gem for Ruby 2.5, to be honest. I'll see what can be done but can't make any promises :(

from lokalise_rails.

Perhaps, the simplest solution is to stay on v3 which is very similar to v4 (the main difference is that it doesn't use multithreading). In this case you should be good as it relies on Faraday 1.

from lokalise_rails.

Now there's a problem with faraday:

1. lokalise_manager v2.2.1 requires ruby-lokalise-api v5.0
2. ruby-lokalise-api v5.0 requires faraday v2.0
3. faraday v2.0 requires Ruby 2.6

Please check all your dependecies chain on Ruby 2.5, so I'm not ought to report it again =)

from lokalise_rails.