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

Non-JSON error messages #4

Open
ryandesign opened this issue Nov 8, 2012 · 2 comments
Open

Non-JSON error messages #4

ryandesign opened this issue Nov 8, 2012 · 2 comments

Comments

@ryandesign
Copy link

When an error occurs, such as "Password and confirmation do not match" or "Request token is invalid", a JSON response is sent.

My app is just a web site, in which I'd like to avoid JavaScript if plain HTML would do. How would I go about getting a plain HTML response to the browser for these error messages?

The documentation should address this, and/or there should be a working example of this.

@kbjr
Copy link
Contributor

kbjr commented Nov 8, 2012

At the moment there is no way to intercept the output before it goes to the client, but it wouldn't be too hard to add in the functionality.

kbjr added a commit that referenced this issue Nov 12, 2012
kbjr added a commit that referenced this issue Apr 13, 2013
@kbjr
Copy link
Contributor

kbjr commented Apr 13, 2013

This feature is in place, but is completely untested.

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