Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

allow naming of scopes #84

Open
chrispitzer opened this Issue Oct 3, 2013 · 16 comments

Comments

Projects
None yet

Currently scopes are listed like so...

scope (123)
...scope (128)
...scope (141)
......scope (142)

This is problematic, because I have to do a lot of digging to find the thing I'm looking for. I propose the following upgrade.

If I have specified the optional property "scope.batarang_name" it will show up as the name of the scope in batarang.

I'm not sure if this will help, but I'm in the process of forking this project to add a controller tree view: here is an example.

You can click on to the controller names to inspect the corresponding elements. So far this only works with explicit controllers (elements with the ngController directive). If you have any ideas for improving it, let me know!

I'm talking specifically about improving this interface

I am renaming the $scope.$id property inside my controllers with something like this:

DEBUG && ($scope.$id += '-APP_CTRL');

which makes it appear as scope (008-APP_CTRL) and even enables multicontroller naming such as 012-FORM_CTRL-PERSON.

The problem is after manually changing the scope id I get { This scope has no models } in dev tools.

gflarity commented Feb 2, 2014

Ya, it's hard to grok without some way of naming things.

nickvido commented May 5, 2014

+1

+5; I'm new to angular though, so would also be interested in hearing if the need for this is the result of some code smell and there is a better way to do things that avoids this.

marcj commented Aug 11, 2014

+6

@btford btford added the enhancement label Aug 11, 2014

I agree, this would really ease finding problematic scope expressions.

rhalff commented Oct 7, 2014

+6.23

temega commented Mar 25, 2015

++1

sakalys commented Oct 9, 2015

++

Member

SomeKittens commented Oct 10, 2015

Commenting +1 won't make this happen any faster - if anyone's interested, we do allow pull requests!

@SomeKittens SomeKittens self-assigned this Nov 12, 2015

@SomeKittens SomeKittens referenced this issue in angular/angular-hint Nov 13, 2015

Closed

feat(name scopes): Allow users to name scopes #115

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment