Skip to content

The markup parser doesn't correctly determine nextParserIndex in most usecases #75

@erikhagreis

Description

@erikhagreis

The markup parser (as prototype of any multi-line parser) does not correctly determine the end of the current multi-line comment segment.

This is the problematic code:

// find the next instance of a parser (if there is one based on the @ symbol)
// in order to isolate the current multi-line parser
var nextParserIndex = block.indexOf('* @', i+1),

I think the indexOf('* @') call assumes a situation where comments are written in the following style example:

/**
 * @markup
 * <button>click</button>
 *
 * @state :hover - When mouse rolls over
 */

If this style of commenting (with leading *'s each line) is not followed, the nextParserIndex will not be detected and the markup section is assumed to last the rest of the comment block. Adding parseable lines below a markup section like in the example above will result in those lines being included in the markup.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions