Format error logs in debug module [issue 9244]

[anish-bhanwala-qp]

What it does

Fixes: #9244
In case where error is logged as console.error(error) it gets stringified to [object Object].
So replaced such occurrences with the format console.error('<Method> failed:', e).
Made changes only for the debug module.

How to test

I tested by manually throwing the error.

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[vince-fugnitto]

@anishbhanwala thank you for your first contribution to the framework 👍

Do you mind updating amending the commit to provide a more meaningful title, at the moment it is your sign-off which does not mean much in the git history:

commit b939b63ee6074253c3b809af19bd1f8255f36f75 (HEAD -> anishbhanwala-debug-module-format_logs_9244)
Author: Anish Bhanwala <[email protected]>
Date:   Wed Apr 21 15:41:12 2021 +0530

    Signed-off-by: Anish Bhanwala <[email protected]>
    
    Related to issue: #9244
    
    In case where error is logged as console.error(error) it gets stringified to [object Object].
    So replaced such occurrences with the format console.error('<Method> failed:', e).

@colin-grant-work I have not followed the discussion closely, should we be prefixing the errors with debug - so errors like setValue or saveAll are more meaningful?

[anish-bhanwala-qp]

@anishbhanwala thank you for your first contribution to the framework 👍

Do you mind updating amending the commit to provide a more meaningful title, at the moment it is your sign-off which does not mean much in the git history:

commit b939b63ee6074253c3b809af19bd1f8255f36f75 (HEAD -> anishbhanwala-debug-module-format_logs_9244)
Author: Anish Bhanwala <[email protected]>
Date:   Wed Apr 21 15:41:12 2021 +0530

    Signed-off-by: Anish Bhanwala <[email protected]>
    
    Related to issue: #9244
    
    In case where error is logged as console.error(error) it gets stringified to [object Object].
    So replaced such occurrences with the format console.error('<Method> failed:', e).

@colin-grant-work I have not followed the discussion closely, should we be prefixing the errors with debug - so errors like setValue or saveAll are more meaningful?

@vince-fugnitto I have updated the commit message. Please check if it makes sense now.

[vince-fugnitto]

@vince-fugnitto I have updated the commit message. Please check if it makes sense now.

Thank you!

[colin-grant-work]

@colin-grant-work I have not followed the discussion closely, should we be prefixing the errors with debug - so errors like setValue or saveAll are more meaningful?

@vince-fugnitto, that's certainly an option, but I don't think it's necessary. The problem before this change is that the log would say only [object Object]. Now that the actual error will appear, it should provide enough information to clarify what's going on.

[vince-fugnitto]

@anishbhanwala the changes look good to me, I look forward to many more contributions in the future!

[anish-bhanwala-qp]

@anishbhanwala the changes look good to me, I look forward to many more contributions in the future!

@vince-fugnitto
Awesome! Thank you!

Yes, I will try to find some issue today. If you have any suggestions that would be helpful.