New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve console/logging support #1546
Comments
@rfwatson have you seen the following crates: |
@jstarry This issue is based on a discussion we had on the Discord server (here). The problem with these crates is that the formatting happens on Rust's end. This prevents browsers from displaying JavaScript objects with the same inspection tools as you would get when logging them through |
Ah that makes sense, thanks |
Where should we go with this now that weblog is a thing? Either way I think we should deprecate/remove the current |
I'd like to see all the services eventually move to external dependencies so I'm totally fine with this |
Happy to work on a patch to integrate the weblog crate if it's useful. |
@jstarry yeah, that's what I'm thinking as well. Glad we're on the same page there. @rfwatson there are still a few features missing from There are also some other console features which |
#1842 and rustwasm/gloo#142 resolved this for the most part. I think the only thing left is toreplace the console calls inside yew with |
Describe the feature you'd like
Improved integration with console/logging in the browser, especially:
console.log
any JsValue*, without pre-encoding to a &str in Rust*or the std_web equivalent, if possible
Is your feature request related to a problem? Please describe. (Optional)
Debugging large objects (e.g. arrays containing audio data) is painful from Rust right now
Describe alternatives you've considered (Optional)
N/A
Additional context (Optional)
N/A
Questionnaire
The text was updated successfully, but these errors were encountered: