-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
responders - rails 4.2 #98
Comments
@matteolc - I haven't tested against rails 4.2 yet. I'll take a look ASAP. |
FYI Here's my application controller: class ApplicationController < ActionController::API include ActionController::Caching def self.respond_to(*mimes) respond_to :json include DeviseTokenAuth::Concerns::SetUserByToken end I had to add def self.respond_to(*mimes) to avoid the error: ActionController::RoutingError (The controller-level I think it's related to warden. Thanks |
So actually all that should be required to make it work when inheriting from ActionController::API is class ApplicationController < ActionController::API include ActionController::MimeResponds def self.respond_to(*mimes) respond_to :json end (Not sure what wasn't working before :O) |
weird..i got it to work, restarted the server, and got again halted before finding the user.. Filter chain halted as :authenticate_account! rendered or redirected I guess validate_token should be called but it's not the first time? (I use ng-token auth) :O |
@matteolc - I just updated to rails 4.2. Can you please check out version |
@matteolc - I just pushed version |
Ok thanks! |
@matteolc - make that |
hi
is token auth ready for rails 4.2 (with responders gem moved out?)
i can't seem to get it to respond to :json ..
thanks
The text was updated successfully, but these errors were encountered: