Telodendria/Telodendria

Utilize MatrixErrorCreate() custom error messages #6

New issue

Closed

opened 2023-09-05 20:04:20 +00:00 by jordan · 0 comments

jordan commented

2023-09-05 20:04:20 +00:00

Owner

Right now, we mostly just pass NULL into pretty much every call to MatrixErrorCreate(). At some point, we need to go through and set descriptive error messages on all these, both to make debugging easier, but also to make sure end users actually know specifically what's going on.

Right now, we mostly just pass `NULL` into pretty much every call to `MatrixErrorCreate()`. At some point, we need to go through and set descriptive error messages on all these, both to make debugging easier, but also to make sure end users actually know specifically what's going on.

jordan added the

label 2023-09-05 20:04:20 +00:00

jordan added this to the (deleted) milestone 2023-09-05 20:16:58 +00:00

jordan added this to the Telodendria v1.7.0-alpha4 project 2023-09-05 20:18:04 +00:00

~~lda referenced this issue 2023-11-02 12:43:44 +00:00~~

Refactor code to comply with #8 #39

lda referenced this issue

2023-12-01 19:57:28 +00:00

Set an error message with MatrixErrorCreate whenever applicable #45

jordan referenced this issue from a commit

2023-12-02 15:24:14 +00:00

Set an error message with MatrixErrorCreate whenever applicable (#45)

jordan closed this issue

2023-12-02 15:24:15 +00:00

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Telodendria/Telodendria#6

No description provided.