You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yet another idea: we’d like to introduce some error handling in RESTXQ. Our current favorite would be to specify a '%rest:error' annotation. If a function is decorated with this annotation, it could be called for certain HTTP codes or XQuery errors. Two examples:
In this proposal, HTTP codes are specified via integers, and XQuery errors are specified as string. We could also introduce two different annotations to make the difference more explicit.
Feedback is welcome!
The text was updated successfully, but these errors were encountered:
Yet another idea: we’d like to introduce some error handling in RESTXQ. Our current favorite would be to specify a '%rest:error' annotation. If a function is decorated with this annotation, it could be called for certain HTTP codes or XQuery errors. Two examples:
In this proposal, HTTP codes are specified via integers, and XQuery errors are specified as string. We could also introduce two different annotations to make the difference more explicit.
Feedback is welcome!
The text was updated successfully, but these errors were encountered: