Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gemspec required Rails 4 - can we drop Rails 3.2 support? #323

Closed
olleolleolle opened this issue Feb 12, 2021 · 3 comments
Closed

gemspec required Rails 4 - can we drop Rails 3.2 support? #323

olleolleolle opened this issue Feb 12, 2021 · 3 comments

Comments

@olleolleolle
Copy link
Contributor

There is a patch in https://github.com/roidrage/lograge/blob/master/lib/lograge/rails_ext/rack/logger.rb which seems to be about Rails 3.

Can this go away? Can it ever be needed, now that the gemspec has:

  s.add_runtime_dependency 'activesupport', '>= 4'
  s.add_runtime_dependency 'actionpack',    '>= 4'
  s.add_runtime_dependency 'railties',      '>= 4'
@bquorning
Copy link

I think only the comment is about Rails 3. Even in Rails 6.1, the Rails::Rack::Logger middleware is adding lines line Started GET "/session/new" for 127.0.0.1 at 2012-09-26 14:51:42 -0700 to the log.

That isn‘t to say that the patch couldn’t be implemented in other ways. For Rails 6.1 (and possibly earlier – I haven’t checked) it seems it would be enough to patch the #logger method to return a Null object responding to #info. (The current patch doesn’t even emit the "request.action_dispatch" event…)

@olleolleolle
Copy link
Contributor Author

Ah, thanks for the deeper insight!

@olleolleolle
Copy link
Contributor Author

#327

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants