Skip to content

Conversation

@osdiab
Copy link
Contributor

@osdiab osdiab commented Oct 19, 2020

I haven't inspected the code to know if string or any other type does get returned, but this can at least inform people without needing to inspect the code that it can be an easily parsable Error instance.

Closes #6933

I haven't inspected the code to know if string or any other type does get returned, but this can at least inform people without needing to inspect the code that it can be an easily parsable Error instance.
Copy link
Contributor

@imnotjames imnotjames left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense - looking at where we call logQueryError it may only be an error but it's unclear. Keeping the string & adding error seems like a good path forward.

@imnotjames imnotjames merged commit c0d691d into typeorm:master Oct 19, 2020
@imnotjames imnotjames added the hacktoberfest-accepted label hacktoberfest label Oct 19, 2020
zaro pushed a commit to zaro/typeorm that referenced this pull request Jan 12, 2021
I haven't inspected the code to know if string or any other type does get returned, but this can at least inform people without needing to inspect the code that it can be an easily parsable Error instance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted label hacktoberfest

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logger typings appear to be wrong

2 participants