Closed bradseefeld closed 12 years ago
At this time, if you are using Rails 3, please use the filter from rubycas-client-rails.
Wait a sec... that gem has one file in it and it still depends on this gem? It looks like you are trying to make rubycas-client rails agnostic which is normally just done by:
# lib/casclient.rb
require "casclient/railtie" if defined?(Rails)
This has no affect on users that arent using Rails. Its the normal way of approaching this problem and it doesnt require someone to include a second gem.
I am not using this for a personal or side project. A core piece of our business will depend on the proper functioning of this gem. I am curious what your roadmap looks like and the reason for some of these changes. What is the best way to talk to you about this?
@bradseefeld, I understand your passion about the situation. My company (and I imagine many others based on the download numbers off of rubygems.org) also depend on this gem working. The line of code you point out was actually a fix for #33. The project needs a lot of work, the rails 3 support being just one area, and I'd love to discuss the roadmap with you. Please send a message to the RubyCas Google Group and I can message you back through there.
This bug was introduced in version 2.3.9. 2.3.8 appears to work just fine. It stems from this line:
https://github.com/rubycas/rubycas-client/blob/master/lib/casclient/frameworks/rails/cas_proxy_callback_controller.rb#L26