Turn off debug output in release #56

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

As of #46, the app prototype writes a lot of haphazardly formatted debug output to the browser console. When we release the app live on the web, console output should be restricted to things that users can understand and benefit from.

If we find that certain debug messages are consistently useful during development, we should use Cargo features to hide them in the live release.

If the usefulness of debug messages tends to be transient, we could instead just remove these messages before merging any pull request that will become a release.

As of #46, the app prototype writes a lot of haphazardly formatted debug output to the browser console. When we release the app live on the web, console output should be restricted to things that users can understand and benefit from. If we find that certain debug messages are consistently useful during development, we should use [Cargo features](https://doc.rust-lang.org/cargo/reference/features.html) to hide them in the live release. If the usefulness of debug messages tends to be transient, we could instead just remove these messages before merging any pull request that will become a release.
Vectornaut added this to the Alpha project 2025-02-27 09:33:42 +00:00
glen added the
maintenance
label 2025-03-12 22:17:15 +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#56
No description provided.