improvements #1
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
openrn/react-native-logging-tools!1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -1,12 +1,46 @@# react-native-logging# React Native Logging ToolsTypo: remove "to" at the end
I would say: "Plug multiple analytics libraries (<-link to the list below->) to your project"
@ -10,3 +43,4 @@---## UsageTypo: bu => be
I would not put too much details in the usage section. I prefer keeping it as light as possible with a complete example. Then, I would create another "API documentation" section with a more detailed documentation of the initialization function and all the existing APIs
@ -1,35 +1,15 @@import { reactotron, reactotronWithRedux } from './reactotron';import { createFirebaseLogger, createSentryLogger } from './loggers';import { IConfig, IReactotron } from './model/config';import { setupReactotron, setupReactotronWithRedux } from './modules/reactotron';I would keep the index.ts light with just the import/export statements. The code could be moved to one or multiple files (it might be better to extract the logic of each feature (logger, crash, reactotron, ...) and put it in a separate file)
Not sure it is a good practice to use console.log in the lib. Maybe we should re-throw the error or at least disable the logs when we are not in DEV mode (or give control of that logs to the project using the library).