infinitered / infinitered/reactotron

Custom Commands broken

Open
#1,123 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
15.6k
Forks
972
PR merge metrics
No merged PRs in 30d

Description

When defining custom commands in ReactotronConfig.js in an Ignite project, after configure, clear and console.log = Reactotron, setting Custom Commands simply does not work. If I remove Custom Commands, Reactotron works perfectly.

Case 1:
Reactotron.onCustomCommand({
command: 'command 1',
title: 'command 1',
handler: () => console.log('hi')
})

Result 1:
Reactotron screen goes pure white when React Native application finishes launching.

Case 2:
Reactotron.onCustomCommand("test", () => console.log("This is an example"))

Result 2:
Nothing happens when you click on the button.

Using Reactotron 2.17.0.680

Contributor guide

Open the contributing guide

Research direction

Start with the React Native setup in ReactotronConfig.js and trace the onCustomCommand calls for both object and string forms. Reproduce the white screen and the unresponsive button, then verify that custom commands register, render, and invoke their handlers without breaking application launch.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.