Incompatible with rails_admin 1.4.x about redis-actionpack HOT 4 CLOSED

@tubbo Thanks for the suggestion, I've updated the middleware check logic accordingly.

from redis-actionpack.

This seems due to the fact that ActionDispatch::Session::RedisStore is actually a subclass of Rack::Session::Redis, not ActionDispatch::Session::AbstractStore.

This line right here should return true because the middleware is indeed a session store which follows the entire API, but it's testing whether it's a direct subclass of the AbstractStore, which it is not, thus it fails.

The solution here is to extract the common functionality from Rack::Session::Redis into modules, allowing both Rack::Session::Redis and ActionDispatch::Session::AbstractStore to share the same functionality. I'll make an issue on redis-store/redis-rack that accompanies this one.

from redis-actionpack.

from redis-actionpack.

Looking at Dalli's implementation of Rack::Session, I believe the problem has more to do with how RailsAdmin is choosing to figure out which of the middleware is your session store. Instead of testing whether the middleware inherits from some base class, RailsAdmin could be looking for a middleware with the class name "ActionDispatch::Session::#{camelized_session_store_name_from_rails_config}", and then it wouldn't matter what the inheritance chain of that middleware was. Additionally, there's nothing preventing two session stores from being in the Rails middleware chain, technically, so this fix doesn't actually solve for all edge cases.

I don't think there's anything to be done in redis-actionpack, and instead the issue should be raised as to how rails-admin is testing for session store middleware in the chain. Gonna close this unless you feel otherwise.

from redis-actionpack.