Changes between Version 1 and Version 7 of Ticket #6923


Ignore:
Timestamp:
09/04/2018 04:05:34 PM (14 months ago)
Author:
sebastian
Comment:

I made it explicit in the issue description. But no, I don't think that we should make it more relaxed. Looking at existing filter lists, I don't see any example of (non-special) comments in between metadata, but having comments follow the metadata (with no empty line in between) seem quite common.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6923

    • Property Priority changed from Unknown to P2
    • Property Cc kvas Lain_13 dimisa scuturic added
  • Ticket #6923 – Description

    v1 v7  
    77 
    88=== What to change === 
    9 Stop parsing special/metadata comments in `lib/synchronizer.js` as soon as we hit the first line after the header that doesn't have the structure of a special comment. 
     9Stop parsing special/metadata comments in `lib/synchronizer.js` as soon as we hit the first line after the header that doesn't match the regular expression `^\s*!\s*(\S.*?)\s*:\s*(.*)`.