You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heard there will be a v4 in the works on the RN show podcast.
Just to give context on how I use it, I'm sticking on v2, tried v3 a while back a had issues I don't remember and just sticked with v2 because if not broken don't fix it :)
I just wanted to provide what a better experience could look like which is making reactron "pages" more modular, and with that moving to the possibility to have community maintained plugins,
I understand that it already has a modular structure code wise, so maybe it's already the planned direction? on that note a public roadmap could be useful for comunication the direction reactotron is going and getting hopefully good feedback from the community
Some api for modules could/should give the ability to run code on the app, I assume for example when you apply a redux state reactotron is running code on the app to do it.
Module idea example 1: Sending push notifications to ios simulator and/or APNS/FCM from reactotron it self.
For a module like this Maybe even ability to run code for specific module, like
console.tron.notifyModule('module_id', 'action_name', 'option_somestring or object(?)'), ie:
console.tron.notifyModule('push_notification_module_xpto', 'register_fcm_token', '')
or console.tron.notifyModule('push_notification_module_xpto', 'un_register_fcmtoken')
Module idea example 2: Metro CLI (or whatever bundler).
Module idea example 2.1: Expo, (?) havent used expo for a while, but could see a usefulness to show the expo start web page
Module idea example 2: RN dev tools, from what I heard you guys are considering having it as part of reactotron
Some ideads would also probably make reactotron more intertwined with a specific app, where right now in theory I can connect 2 completely different apps, so reacotron would need to support opening/specifying a directory so it know where to run things.
Also another possible feature is CLI integration: Not sure about real pratical cases related to reactotron as a develpment/debug tool. So not important but worth considering, for example I love the fact I can apply a redux snapshot, if we could do that with a command in shell it could be very useful for e2e testing. I say is not important because it's a single random use case, but having ability to for example run code on the app, ie to modify asyncstorage could be cool but likely outside of scope of reactotron.
_Would also be interesting to see reactotron (re?)-built with react native targetting windows/macos/linux(?)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Heard there will be a v4 in the works on the RN show podcast.
Just to give context on how I use it, I'm sticking on v2, tried v3 a while back a had issues I don't remember and just sticked with v2 because if not broken don't fix it :)
I just wanted to provide what a better experience could look like which is making reactron "pages" more modular, and with that moving to the possibility to have community maintained plugins,
I understand that it already has a modular structure code wise, so maybe it's already the planned direction? on that note a public roadmap could be useful for comunication the direction reactotron is going and getting hopefully good feedback from the community
Some api for modules could/should give the ability to run code on the app, I assume for example when you apply a redux state reactotron is running code on the app to do it.
Module idea example 1: Sending push notifications to ios simulator and/or APNS/FCM from reactotron it self.
For a module like this Maybe even ability to run code for specific module, like
console.tron.notifyModule('module_id', 'action_name', 'option_somestring or object(?)'), ie:
console.tron.notifyModule('push_notification_module_xpto', 'register_fcm_token', '')
or console.tron.notifyModule('push_notification_module_xpto', 'un_register_fcmtoken')
Module idea example 2: Metro CLI (or whatever bundler).
Module idea example 2.1: Expo, (?) havent used expo for a while, but could see a usefulness to show the expo start web page
Module idea example 2: RN dev tools, from what I heard you guys are considering having it as part of reactotron
Some ideads would also probably make reactotron more intertwined with a specific app, where right now in theory I can connect 2 completely different apps, so reacotron would need to support opening/specifying a directory so it know where to run things.
Also another possible feature is CLI integration: Not sure about real pratical cases related to reactotron as a develpment/debug tool. So not important but worth considering, for example I love the fact I can apply a redux snapshot, if we could do that with a command in shell it could be very useful for e2e testing. I say is not important because it's a single random use case, but having ability to for example run code on the app, ie to modify asyncstorage could be cool but likely outside of scope of reactotron.
_Would also be interesting to see reactotron (re?)-built with react native targetting windows/macos/linux(?)
Edit: closing as most is being addressed
Beta Was this translation helpful? Give feedback.
All reactions