Funny treatment of whitespace

[tomek-he-him]

getComments('code\n/** comment */\ncode', true)
//» [ { start: 5,
//      end: 19,
//      type: 'Block',
//      loc: { start: [Object], end: [Object] },
//      api: false,
//      value: '* comment ',
//      after: 'code' } ]

getComments('code /** comment */ code', true)
//» []

getComments('code\n/** comment */ code', true)
//» []

getComments('code /** comment */\ncode', true)
//» []

The majority of text parsers I know of – in the web (HTML, JS, CSS) and in Unix (bash and the like) – makes no difference between whitespace characters. It’s enough that there is at least one of the characters [ \n\t] between things so that they are read as separate.

That’s what I’d expect of your tool – and most other users as well, I guess.

[tunnckoCore]

Hm. That's strange... it is handled on #L61 and #L78

But all that issues are normal. Try acorn-exctract-comments.

Also want to mention that it's not faster than jonschlinkert/extract-comments

[tomek-he-him]

Also want to mention that it's not faster than jonschlinkert/extract-comments

Which one do you mean exactly? The acorn thing or yours?

[tunnckoCore]

or yours

mine, get-comments

But acorn-extract-comments also is mine, need bench testing.

I'll come back to them (*-comments) soon.