We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
What should we do in API when things go wrong? Raise expections? Return null?
Consensus on the telecon was that we shoud raise exceptions in case of error and just return valid data.
What should we if your frame didn't match your input?
Most people opted for returning {} at the telecon but there might be some implications that should be further investigated.
The text was updated successfully, but these errors were encountered:
See also follow up on the mailing list by Dave Longley: http://lists.w3.org/Archives/Public/public-linked-json/2011Aug/0078.html
Sorry, something went wrong.
1c8cc49
The API was updated to throw exceptions when things go wrong. null is returned in the framing code when a frame has no match.
http://json-ld.org/spec/ED/json-ld-api/20120112/#the-application-programming-interface
No branches or pull requests
What should we do in API when things go wrong? Raise expections? Return null?
Consensus on the telecon was that we shoud raise exceptions in case of error and just return valid data.
What should we if your frame didn't match your input?
Most people opted for returning {} at the telecon but there might be some implications that should be further investigated.
The text was updated successfully, but these errors were encountered: