rev087/ng-inspector

Route controllers not labelled

Open

#145 opened on Sep 30, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (787 stars) (100 forks)batch import
enhancementhelp wanted

Description

It would be nice if the scope header for views showed the name of the controller like with other components. Currently it shows nothing.

http://plnkr.co/edit/kpYTT5QgDmv4ZntKND2Z

And as long as this is a feature request, I'm gonna say it would be nice to be able to see the route object itself there too. :smile:

Contributor guide

Tech stack
javascripthtmlcss
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
AngularJS basicsunderstanding of scope hierarchy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the ng inspector source code to understand how controller names are resolved for other components. Look at the current scope header rendering logic in the AngularJS inspector. An example plnkr is provided but may be outdated. Determine if the controller name is accessible from the scope object and how to display it. Consider also showing the route object.