search

coffeedoc / codo

CoffeeScript API documentation generator. It's like YARD but for CoffeeScript!
Other
625 stars 92 forks source link

RangeError: Maximum call stack size exceeded #195

Closed aseemk closed 8 years ago

aseemk commented 9 years ago

Running the latest Codo 2.0.9 with CoffeeScript 1.8, I'm unable to parse it against some new code I've written. Every time I try, I get this error:

/Users/aseemk/Projects/Node/neo4j/node_modules/codo/lib/entities/class.coffee:331
          properties = _this.parent.properties.map(function(property) {
                                               ^
RangeError: Maximum call stack size exceeded

These are my .codoopts:

--name 'Node-Neo4j API Documentation'
--title 'Node-Neo4j API Documentation'
--readme API_v2.md
--output docs
./lib-new

When I add --debug and --verbose, I get this:

info: Parsing Extra file /Users/aseemk/Projects/Node/neo4j/API_v2.md
info: Parsing Extra file /Users/aseemk/Projects/Node/neo4j/CHANGELOG.md
info: Parsing Extra file /Users/aseemk/Projects/Node/neo4j/LICENSE
info: Parsing Extra file /Users/aseemk/Projects/Node/neo4j/README.md
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/GraphDatabase.coffee
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/Node.coffee
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/Relationship.coffee
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/Transaction.coffee
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/errors.coffee
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/index.coffee
info: Parsing Codo file /Users/aseemk/Projects/Node/neo4j/lib-new/utils.coffee

/Users/aseemk/Projects/Node/neo4j/node_modules/codo/lib/entities/class.coffee:331
          properties = _this.parent.properties.map(function(property) {
                                               ^
RangeError: Maximum call stack size exceeded

That made me think the culprit might be utils.coffee, but that's a really simple file. I've even tried erasing all of it (and just replacing it with a module.exports = 5), but same exact output.

I can try debugging this on my end a bit more, but I thought I'd post here first. =) Thanks!

inossidabile commented 8 years ago

Fixed.