Turn off debug output in release #56

New issue

Open

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

Vectornaut commented

2025-02-27 09:28:16 +00:00

Collaborator

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.