Class docstring is null when using tabs for indenting about coffeedoc

[omarkhan]

Thanks for this. The issue wasn't tab-related, it was happening for all class definitions without an extends clause. Probably caused by a change in the coffeescript compiler. Fixed in f72d61f

[patriksimek]

Thank you for the quick response, I have another scenario for you to look at. In my classes I use shorthand for property definition which obviously causes another problems...

###
file desc
###

class MyClass
    ###
    class desc
    ###

    fce: ->
        ###
        function desc
        ###

    @property 'hello',
        get: -> 'world'

Output is identical to previous one.

[{
        "docstring": "file desc\n",
        "deps": {},
        "classes": [{
                "name": "MyClass",
                "lineno": 4,
                "docstring": null, // <- empty
                "parent": null,
                "staticmethods": [],
                "instancemethods": [{
                        "name": "fce",
                        "lineno": 9,
                        "docstring": "function desc\n",
                        "params": []
                    }
                ],
                "privatemethods": []
            }
        ],
        "functions": [],
        "privateFunctions": [],
        "path": "test.coffee",
        "basename": "test.coffee"
    }
]

Best,
Patrik

[omarkhan]

Not much I can do there, coffeedoc uses static analysis to find functions and methods, so it won't pick up anything you're assigning dynamically. You can fork coffeedoc and hack on it till it fits your use case

[patriksimek]

I don't want coffeedoc to parse docstring for my dynamic property, I only want it to parse docstring for class correctly even if I use @anything directly in class definition. In my opinion, this is something coffeedoc should do in every case.

[omarkhan]

Oops, you're right. Thanks for that - fixed in 72556ef

[patriksimek]

Thanks, works great now 👍