Make TrinoQueryError::error_location optional
#535
Conversation
|
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
stephen-zhao
changed the title
error_location optionalTrinoQueryError::error_location optional
| return (location["lineNumber"], location["columnNumber"]) | ||
| def error_location(self) -> Optional[Tuple[int, int]]: | ||
| location = self._error.get("errorLocation", None) | ||
| return (location["lineNumber"], location["columnNumber"]) if location else None |
There was a problem hiding this comment.
We could use get for these sub-accesses as well.. and have the whole thing get eaten up by a null if anything doesn't exist.
There was a problem hiding this comment.
Yes, please do so. Then we will be consistent in using get over [].
|
@cla-bot check |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Description
Fix #534 by making
TrinoQueryError::error_locationusinggetinstead of[]to return an optional tuple.Non-technical explanation
Make
TrinoQueryError::error_locationexception-safe when noerror_locationis available.Release notes
( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(x) Release notes are required, with the following suggested text: