Curate debug output #57

Open
opened 2025-02-27 09:33:26 +00:00 by Vectornaut · 0 comments
Collaborator

As of #46, the debug messages that we write to the browser console are:

  • Hard to scroll through.
  • Not very self-explanatory.
  • Often tailored to problems that have now been resolved.

We should decide which debug messages, if any, are consistently useful during development. We should then format those messages in a way that makes them more self-explanatory and easier to scroll through.

As of #46, the debug messages that we write to the browser console are: - Hard to scroll through. - Not very self-explanatory. - Often tailored to problems that have now been resolved. We should decide which debug messages, if any, are consistently useful during development. We should then format those messages in a way that makes them more self-explanatory and easier to scroll through.
glen added the
maintenance
label 2025-03-12 22:16:53 +00:00
Sign in to join this conversation.
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: glen/dyna3#57
No description provided.