bug(0.7.2): No Models show up when clicking on a Scope item

[clabough]

No Models show up when clicking on a Scope item.

Clicking on the scopes item in the left navigation clears the window.

[btford]

Can you please provide a reproduction via jsbin, plnkr.co, or jsfiddle? This saves me a lot of time. Thanks!

[clabough]

Happens on any Angular page. Here's a sample app from plnkr.co

http://screencast.com/t/ssPbpDIxpV

http://plnkr.co/edit/lIzdAA9FHlDU7boiYugr?p=preview

[btford]

thanks! Looking into it now.

[smerse]

Edit: Sorry using Version 0.7.4

I think the repeating 'information' so many times is that right ?

Name controllers according to best practices (7) Controller names should start with an uppercase character and end with the suffix Controller. For example: UserController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController. Consider renaming plunkerCatalogueController to PlunkerCatalogueController.

Example above: http://plnkr.co/edit/lIzdAA9FHlDU7boiYugr?p=preview

[btford]

@smerse – this is a totally unrelated issue.

[ilanbiala]

The issue also seems to exist in 0.7.4.

[rogerwaldvogel]

Have the same problem in 0.7.4

[gtesslerge]

I agree. v 0.7.4 is totally broken. No way to see ANY model information. Baratang is useless in current state. Bring back the old working UI until this is fixed please.

[sroberson]

I agree with @gtesslerge. Can we roll back to a previous release? Perhaps I can investigate compiling from source?? Oh, I don't need to. I can just use the old 0.4.3 version from the releases. Awesome. I can use Batarang again!

[ibigbug]

Same problem :(

[dmglab]

Same Problem... (0.7.4)

[Symmetric]

@btford, can you guys roll back the Chrome extension to a functioning version? For everyone who's found this bug report, there's probably tens or hundreds of less-savvy users who have been spinning their wheels for the week that this extension has been broken.

For those looking for a workaround, the README in this project has instructions for how to load previous versions directly from source; it's very straightforward. I rolled back to 0.4.3 and the extension is working again.

For the record, I tested builds 0.7.1, 0.7.0, and 0.6.1, and they were all borked. Couldn't be bothered to test any of the other releases that were cut in the last week, so I just rolled back to an older version from a date when I knew this extension was working. Not really sure why all those releases were cut when they didn't work at all, but hey.

[nathan-munchery]

A status update at some point would be helpful as well. 6 days is a long time.

[ilanbiala]

@nathan-munchery he doesn't do this because he's commanded, he's doing it to improve the support around Angular, so if you want to add a fix, feel free to, but don't be mean to someone who is already doing so much for the AngularJS community.

[orangeloop]

@ilanbiala Why is asking for a status update mean? The extension is clearly broken for many people - just read the comments in the chrome store and elsewhere. I don't think asking for some kind of status is too much to ask.

[ilanbiala]

I want one too, but people are being rude about it and they have very little right to. This is free and open source, anyone can add and it shouldn't be all one person.

[jonesmac]

@orangeloop it would be more helpful to just point people on the chrome store and github to the repo homepage on how to install previous versions. 0.4.3 works great for me.

[dmglab]

@jonesmac awesome Idea. But couldn't we just "rewind" the new Version?

And: How the heck could any Version above 0.4.3 got “stable” for Chrome Store ?

[nathan-munchery]

@ilanbiala I think we are in agreement that one person should not be responsible for this entire project, but that seems to be the way that Google wants to keep it.

[ilanbiala]

@nathan-munchery just ask @btford @caitp for some guidance and start opening PRS. After a while you will be a collaborator.

[Symmetric]

@ilanbiala the pragmatic quick fix here is to roll back the version that's in the Chrome store, and that's something that only the project owners can do.

[uberDoward]

Selecting a scope loads no models here, either. V 0.7.4 Rolling back to 0.4.3 so I can use a working version of Batarang.

[ilanbiala]

Has a fix for 0.7.4 been released yet @btford?

[SomeKittens]

Fixed in master, will be released in 0.8.0