-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add remoteObjectParseError #1134
Conversation
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.
👍
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.
LGTM.
786b0b8
to
5561e9e
Compare
f3e332c
to
3bcb2e2
Compare
133793b
to
feafa26
Compare
The base branch was changed.
3bcb2e2
to
82fb803
Compare
This error can be used to encapsulate the details when a remote object can not be parsed successfully.
When the json parsing fails we should work with remoteObjectParseError so that we can hopefully identify what exactly cannot be parsed.
82fb803
to
bda54b9
Compare
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.
🤞
What?
Adds a new
remoteObjectParseError
error type.Why?
For use when parsing of remote objects fails. It should hopefully help identify what exactly failed to parse.
Checklist
Related PR(s)/Issue(s)
Updates: #987