MetaMask / MetaMask/metamask-extension
Initialize the logging controller in the extension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Description
The Logging controller, once merged into the core monorepo, will provide the ability for engineers to add log points throughout the application for highly valuable information for customer support, metamask engineers, and end users. However, before it can be utilized, it must be initialized in the metamask-controller within the extension. By initializing the controller, even if we do not use it anywhere, we make all controllers that extend the BaseControllerV2 able to eventually use the messaging system to invoke log points in their own code.
Steps:
1. Import new @metamask/logging-controller package in extension
2. Initialize the controller passing it a restricted message manager prop
3. profit.
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
Use the extension's metamask-controller initialization as the entry point; compare nearby controller setup and the @metamask/logging-controller initialization API. Done means the logging controller is imported, initialized with a restricted message manager, and available to controllers extending BaseControllerV2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100