-
Notifications
You must be signed in to change notification settings - Fork 60
Backbone.js class style not recognized #8
Comments
Hi ggerrietts, can you say more about the submodule errors you're getting? Anybody that clones the doctorjs code and does submodule-init/update should be able to get the narcissus code. I'm curious why it's not working for you. |
If you can read past my funky shell prompt, this should illustrate the problem I'm having:
|
whoops, "close" means issue, not dialog. >.< |
OK, the submodule issue should be fixed now in the latest commit. |
The submodule issue is now fixed, yes. Thanks! |
Using the current recipe for executing jsctags.js, the source of todos.js crashes:
|
Pull now, it should work. |
I can confirm that it now works at least as well as it did in f63c1e0d30bd8a15823e. Function tags are still the only tags being generated, and I assume it's because of the style employed by Backbone.js applications. |
I would love to see tags generated for Backbone.js classes as well. |
I would like to see this work for Ember.js also. The |
I can't tell for sure whether this is a usage pattern problem, but if I feed jsctags the source of the [Todos example][http://documentcloud.github.com/backbone/examples/todos/todos.js] featured in the Backbone.js documentation, I get a sequence of function tags back out. Top-level names like window.Todo and window.Todolist aren't generating tags, and neither are non-function properties like model or events. I can understand why the backbone-style classes aren't recognized as classes, but as a consequence, none of the functions are identified as part of the classes, either.
I'm not sure if there's a usage pattern that I'm not familiar with, or a way of indicating dependencies, or a flag for turning on output of variables. I'm also not sure if maybe this is fixed downstream of where I'm working (commit f63c1e0), to work around the problems I've been having with the narcissus submodule not responding properly to the submodule init/update commands (it wants SSH access) and the follow-on build problems reported elsewhere.
Despite my uncertainty, I did want to make sure someone was aware of the issue.
The text was updated successfully, but these errors were encountered: