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

Best effort error handling when cloud code returns unexpected data #232

Closed
cheungpat opened this issue Nov 16, 2016 · 0 comments
Closed
Assignees

Comments

@cheungpat
Copy link
Contributor

cheungpat commented Nov 16, 2016

Coding error can cause cloud code runtime to return unexpected data. Instead of returning a parse error to the user, the error object could provide more information.

Currently skygear-server returns this:

{"error":{"name":"UnexpectedError","code":10000,"message":"failed to parse response: json: cannot unmarshal string into Go value of type common.ExecError"}}
cheungpat added a commit to cheungpat/skygear-server that referenced this issue Nov 17, 2016
cheungpat added a commit to cheungpat/skygear-server that referenced this issue Nov 17, 2016
@cheungpat cheungpat self-assigned this Nov 17, 2016
cheungpat added a commit to cheungpat/skygear-server that referenced this issue Nov 17, 2016
cheungpat added a commit to cheungpat/skygear-server that referenced this issue Nov 17, 2016
cheungpat added a commit to cheungpat/skygear-server that referenced this issue Nov 18, 2016
@rickmak rickmak closed this as completed Dec 5, 2016
@rickmak rickmak removed the In Review label Dec 5, 2016
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