Skip to content
This repository has been archived by the owner on Mar 15, 2023. It is now read-only.

Need to return proper errors #3

Closed
ekryski opened this issue Apr 10, 2014 · 4 comments
Closed

Need to return proper errors #3

ekryski opened this issue Apr 10, 2014 · 4 comments

Comments

@ekryski
Copy link
Member

ekryski commented Apr 10, 2014

For example:

  • Not Found
  • Bad Request
  • Internal Server Error
  • etc.

Feathers can then catch these errors and then proxy them back to client as it sees fit.

@daffl
Copy link
Member

daffl commented Apr 10, 2014

Do we need general Feathers error objects that services can share for that? Also should this repository be called feathers-mongoskin?

@ekryski
Copy link
Member Author

ekryski commented Apr 10, 2014

I think we do need a general feathers-errors module that is shared. Don't feel like copying that all over the place.

@ekryski
Copy link
Member Author

ekryski commented Apr 10, 2014

But no I don't think this should be called feathers-mongoskin. The library we are using to connect and make queries shouldn't matter. The only special case is feathers-mongoose because it is an ORM that supports schema's and stuff.

@daffl
Copy link
Member

daffl commented Apr 10, 2014

That makes sense. Ideally you shouldn't really see anything about the library.

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

No branches or pull requests

2 participants