-
Notifications
You must be signed in to change notification settings - Fork 8
Feature/prefix #42
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
Feature/prefix #42
Conversation
…modifications to git stage.
| } | ||
|
|
||
| if (err) | ||
| return { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you do not need to return from try block, throw is suffice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, Actually we don't need to throw it. Because:
- It's a proxy request from contentstack to user.
- In our error middleware we cannot throw an error with an object, we're throwing message with status.
| fileName | ||
| ); | ||
|
|
||
| return { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return not needed from try
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, Actually we don't need to throw it. Because:
- It's a proxy request from contentstack to user.
- In our error middleware we cannot throw an error with an object, we're throwing message with status
No description provided.