Skip to content
New issue

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

When error occurs, print out path where in the code the issue occurred/increase verbosity #185

Open
ibutab opened this issue Sep 7, 2024 · 3 comments
Labels
enhancement New feature or request
Milestone

Comments

@ibutab
Copy link

ibutab commented Sep 7, 2024

Is your feature request related to a problem? Please describe.
I'm making a game with lots of different queries, this makes it difficult to have verbosity on (if I'm not developing a specific query). Sometimes I get errors, e.g "--> SQL error: NOT NULL constraint failed: horse_training.ht_effort". In some cases I can't even turn on vebosity, because the Godot console would stop printing. The issue is that I have multiple different functions that can have a query with similar stuff, this makes it very hard to backtrack where the issue is.

Describe the solution you'd like
I would like to in someway, when there is an error, be able to increase verbosity or more easily find out where the query originated from. So say --> SQL error: NOT NULL constraint failed: horse_training.ht_effort. Query origination: script path, line number".

Describe alternatives you've considered
Have not considered alternatives.

@ibutab ibutab added the enhancement New feature or request label Sep 7, 2024
@ibutab
Copy link
Author

ibutab commented Sep 7, 2024

@2shady4u

@2shady4u
Copy link
Owner

2shady4u commented Sep 9, 2024

Hello @ibutab,

This should be doable by using the push_error()-method which automatically adds this information to the error message in Godot itself.
Unfortunately, I currently don't have time to work on this enhancement... 😢
I'll try to get back to this issue once I have time again.

@ibutab
Copy link
Author

ibutab commented Sep 9, 2024

Ok, no problem. I'll see what I can do with push error 👍 @2shady4u

@2shady4u 2shady4u added this to the v4.5 milestone Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants