Bogdan Gusiev

> I understand such changes in Range filters are more or less backward-incompatible. A major-version upgrade in versioning may be necessary? Personally, I would accept and welcome the breaking changes...

@masasakano I've addressed all the issues with discussed here. I would apreciate if you try #328 `version-2` branch in your project and provide feedback on how difficult is the upgrade...

> New I18n-Translation of **.datagrid.filters.range.separator was newly introduced Updated. > Serialization/Deserialization of Range is help correctly Typo: help => held > CSS Class for the Datagrid table tag used to...

> (another) W3C validation failure Fixed. > Did you mean "hard-coding" instead of "hardcore"? Fixed. > @grid = ArticlesGrid.new(order: :release_date, **prms) That is valid concern. Datagrid was desinged before `**`...

Yeah, I guess so. It would be better if it would serialize `LazyMapCollection` properly because why not or throw an error that it can't. Anyway, whatever you decide on it.

I came up with this in one day: ``` ruby # frozen_string_literal: true require 'test_helper' class ApplicationEntityTestCase < ActiveSupport::TestCase ACCEPTIBLE_CLASSES_MAP = { "DateTime" => [Time, DateTime, ActiveSupport::TimeWithZone, String], "Boolean" =>...

I am calling `pg_format` executive from ruby program. It takes ~200ms to do, which is way too slow. If I can keep a running process in memory and interact with...

I think that the first step in this direction should be general `where.exists` and `where.not_exists` methods: ``` ruby User.where.exists(Post.where("users.id = posts.user_id")) User.where.not_exists(Post.approved.where("users.id = posts.user_id") ``` I would consider a patch...

> We can already do something like this with `arel.exists` chain, like, > > ```ruby > User.where(Post.where("users.id = posts.user_id").arel.exists) > # SELECT "posts".* FROM "posts" WHERE EXISTS (SELECT "authors".* FROM...

Is there any way we can work it around at the ruby level?