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

Handle errors #1

Open
talum opened this issue Jan 31, 2017 · 7 comments
Open

Handle errors #1

talum opened this issue Jan 31, 2017 · 7 comments

Comments

@talum
Copy link
Owner

talum commented Jan 31, 2017

and display message to user

@talum
Copy link
Owner Author

talum commented Feb 15, 2017

http://travisjeffery.com/b/2012/04/rendering-errors-in-json-with-rails/

  • Need to return a status code of 422
  • @object.errors.full_messages
  • Should there be a generic errors component? Or keep it isolated?

@talum
Copy link
Owner Author

talum commented Feb 16, 2017

Uploading Screen Shot 2017-02-16 at 5.16.12 PM.png…

wat

@talum
Copy link
Owner Author

talum commented Feb 17, 2017

React doesn't unmount and remount the components...so will likely need to just fetch all the data and filter client side.

@talum
Copy link
Owner Author

talum commented Feb 17, 2017

@talum
Copy link
Owner Author

talum commented Feb 18, 2017

Few more theories:

  1. dispatch in middle of dispatch
  2. first model data resolves before associated data resolves
  3. doing something wrong with how the router renders the components

@talum
Copy link
Owner Author

talum commented Feb 18, 2017

screen shot 2017-02-18 at 5 30 01 pm

@talum
Copy link
Owner Author

talum commented Mar 16, 2017

Could handle these a little better --> server errors getting caught and parsed

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

1 participant