Eric Bailey
66af8f1fbf
* Migrate logEvent to useAnalytics * Migrate logger.metric to useAnalytics * Migrate tricky spot, fix types * Migrate remaining tricky spot * Missed one * Remove metric() from logger * Migrate useGate to useAnalytics * Remove all other StatSig mentions * Update event payload * Update logger tests * Mock expo method
Logger
Simple logger for Bluesky.
At a Glance
import { logger, Logger } from '#/logger'
// or, optionally create new instance with custom context
// const logger = Logger.create(Logger.Context.Notifications)
// for dev-only logs
logger.debug(message, {})
// for production breadcrumbs
logger.info(message, {})
// seldom used, prefer `info`
logger.log(message, {})
// for non-error issues to look into, seldom used, prefer `error`
logger.warn(message, {})
// for known errors without an exception, use a string
logger.error(`known error`, {})
// for unknown exceptions
try {
} catch (e) {
logger.error(e, {message: `explain error`}])
}
Log Levels
Log level defaults to info. You can set this via the EXPO_PUBLIC_LOG_LEVEL
env var in .env.local.
Filtering debugs by context
Debug logs are dev-only, and not enabled by default. Once enabled, they can get
noisy. So you can filter them by setting the EXPO_PUBLIC_LOG_DEBUG env var
e.g. EXPO_PUBLIC_LOG_DEBUG=notifications. These values can be comma-separated
and include wildcards.