RocketChat / RocketChat/Rocket.Chat.ReactNative
Bugsnag optional for whitelabel builds
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 1.5k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 90
Description
Description:
This is related to #2971, but for different reasons. I support a number of government customers that would like to bring Rocket.Chat into their enterprise. One reason why applications like Rocket.Chat are invaluable to the government is the ability to host these systems internally. Restrictions when running on a government system are high, one of these being communication with external 3rd party systems. Unfortunately running with bugsnag enabled is a non starter. Would it be possible to look into adding an option to disable bugsnag when building the whitelabel apps?
Environment Information:
- Rocket.Chat Server Version: 13.12.1
- Rocket.Chat App Version: 4.15.0
- Device Name: Any
- OS Version: Any
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by tracing the whitelabel app build configuration and where Bugsnag is initialized, then determine how a build can disable it; done means whitelabel builds complete without Bugsnag communication while the default builds retain it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100