Closed andrejak closed 5 years ago
Plugins might need to define for themselves how their state should be rendered - e.g. for the firestore plugin, I wouldn't really want to see the db_cache
(but perhaps would be fine if it was just called db
)
At the moment, the firestore plugin can customize it only to the extent of choosing which variables to expose (eg. call exposeUniverseVariables(["db", "db_cache"]) will expose both, whereas exposeUniverseVariables(["db"]) would keep db_cache hidden). (Neither has actually been added yet, I only added route and local so far) Did you have in mind a custom rendering function that would filter data to a more granular level, or change how it's displayed?
@coffee-cup this should be ready for re-review :)
Some minor suggestions
State (editable)
{
}
Plugin State
{
}
Do these look allright to you?
Only app state, no plugin state
Both app state and plugin state
No app state (but plugin state)
I like them!
Shows exposed plugin states (for example route and local) in devtools state panel. At least partially closes https://github.com/prodo-ai/prodo/issues/118.
(in the below screenshot, the app has no internal state, just route)
With empty app state, we could instead show this (ignore color change):