You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that all information about an Intl.Locale is captured in its serialized form and that such serialized forms are typically short, it might make sense to log that info, something like this:
However, the full serialization is only available by calling toString, so possibly not appropriate for logging. Given that many common usages of locales don't use any of the extensions (calendar, hourCycle, etc.) simply showing the baseName might also suffice:
I guess there might be quite a few similar built-ins that don't have good logging in Deno (or Node for that matter) but could have properties exposed to logs to improve that experience. Obviously it makes sense to log things like file names for File objects (#20414 and #20415), but to what extent is it considered useful to do the same for APIs that might be less commonly used?
The text was updated successfully, but these errors were encountered:
Default logging (
console.log
, repl, etc) forIntl.Locale
objects looks like this:Given that all information about an
Intl.Locale
is captured in its serialized form and that such serialized forms are typically short, it might make sense to log that info, something like this:However, the full serialization is only available by calling
toString
, so possibly not appropriate for logging. Given that many common usages of locales don't use any of the extensions (calendar, hourCycle, etc.) simply showing thebaseName
might also suffice:I guess there might be quite a few similar built-ins that don't have good logging in Deno (or Node for that matter) but could have properties exposed to logs to improve that experience. Obviously it makes sense to log things like file names for
File
objects (#20414 and #20415), but to what extent is it considered useful to do the same for APIs that might be less commonly used?The text was updated successfully, but these errors were encountered: