Codeblocks styling in COMPUTE-ATTR

[vdragsic]

Fixed codeblocks styling, #1029

[daffl]

Maybe we can still change the flags from

@codestart
var Person = can.Map.extend({
    fullName: function(){
        return this.attr("first") + " " + this.attr("last")
    }
})
var me = new Person({first: "Justin", last: "Meyer"})
@codeend

To tab or space indentation for this PR

    var Person = can.Map.extend({
        fullName: function(){
            return this.attr("first") + " " + this.attr("last")
        }
    })
    var me = new Person({first: "Justin", last: "Meyer"})

[booc0mtaco]

Forgot to ask yesterday... What's wrong with @code{start | end}? Is it a change we want for convention's sake, or do those tags lead to problems elsewhere?

Related, looks like the example above uses spaces. Do we prefer spaces over tabs, vice versa, or does that not matter?

[vdragsic]

@daffl I'll update it, thanks for the tip

[daffl]

@booc0mtaco I think we should use actual markdown and not clutter it with custom tags. @param directives are a convention from documenting code and not part of any Markdown specification.

For the future I'd also like DocumentJS to also parse the YAML frontmatter for markdown files instead of having to add things like the @page and @parent tokens.

[justinbmeyer]

Yes, use markdown where we can.

Sent from my iPhone

On Jun 6, 2014, at 9:56 AM, David Luecke notifications@github.com wrote:

@booc0mtaco I think we should use actual markdown and not clutter it with custom tags. @param directives are a convention from documenting code and not part of any Markdown specification.

For the future I'd also like DocumentJS to also parse the YAML frontmatter for markdown files instead of having to add things like the @page and @parent tokens.

—
Reply to this email directly or view it on GitHub.