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.

Sign up for GitHub

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

Jump to bottom

Better 'Fab' responses #13

Open
gpennington opened this issue Mar 14, 2012 · 3 comments
Open

Better 'Fab' responses #13

gpennington opened this issue Mar 14, 2012 · 3 comments
Milestone
0.2

Comments

@gpennington
Copy link
Member

Many of the exceptions raised have the same message. It should explicitly say what the error was.
@dstegelman
Copy link
Member

  • Return response from stitch even if it fails. - 500?
  • Return error code if stitch couldn't find the method. - 500?

@gpennington
Copy link
Member Author

Yes. But better Status Codes and Messages.

"Yo shit broke because this and that."

instead of

"Yo shit broke."

@dstegelman
Copy link
Member

Well yes, i was saying the return the message, and then the status code as well.

@ghost ghost assigned dstegelman Mar 14, 2012
dstegelman added a commit that referenced this issue Mar 14, 2012
@dstegelman
Small work against issue #13.
a93a65e
@dstegelman dstegelman removed their assignment Jun 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.2
Development

No branches or pull requests
2 participants
@dstegelman @gpennington