One of the things that the Inspector could do really well is show you when bad things happen during the course of using your application. Two very common problems are views being too aggressively rendered (rendered many times in a second) and renders taking too long (a single render taking >500ms).
The inspector logs all of the view and model trigger events and can report when these bad things happen. We could collect these warnings in the UI View info panel in a separate warnings pane.
Implementation
Update patchComponentTrigger and add more metadata
Add findTargetActivity function to the activityCollection where the trigger events are kept in the inspector
Add presentWarnings a utility function to the viewMoreInfo class, which shows the view info panel
Problem
One of the things that the Inspector could do really well is show you when bad things happen during the course of using your application. Two very common problems are views being too aggressively rendered (rendered many times in a second) and renders taking too long (a single render taking >500ms).
The inspector logs all of the view and model trigger events and can report when these bad things happen. We could collect these warnings in the UI View info panel in a separate warnings pane.
Implementation
patchComponentTrigger
and add more metadatafindTargetActivity
function to theactivityCollection
where the trigger events are kept in the inspectorpresentWarnings
a utility function to theviewMoreInfo
class, which shows the view info panelPatch
patch
People
@joshbedo - currently working on this @jasonLaster - advising on the project