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
We have err:XS0107 for static errors in XPath expressions, but nothing equivalent for dynamic errors. We often have specific errors for specific problems, but we need a catch-all. (Reporting err:XS0107 is just...wrong)
The text was updated successfully, but these errors were encountered:
This has to raise an error because the XPath expression in select has an error for the integer parameter.
But currently there is no error code for this. So my implementation has to use the generic XD0030. I would prefer an other error code being directly related to the XPath expression.
In the past few days, Achim and I have both stumbled over how to report errors in XPath expressions that aren't detected until runtime. For some errors of this form, we have specific error codes, but there's no general catch-all for "it didn't work." My implementation has been using err:XS0107, the static version of "invalid expression", but that's really inappropriate for a dynamic error.
I'm not sure where to add this to the specification, but I don't expect any pushback on the requirement, so I've proactively created a dynamic error for it:
err:XD0083: It is a dynamic error if an XPath expression cannot be evaluated, e.g. because the expression is not syntactically valid, contains reference to unknown variables, or makes use of undeclared functions.
ndw
linked a pull request
Dec 14, 2024
that will
close
this issue
We have
err:XS0107
for static errors in XPath expressions, but nothing equivalent for dynamic errors. We often have specific errors for specific problems, but we need a catch-all. (Reportingerr:XS0107
is just...wrong)The text was updated successfully, but these errors were encountered: