Allow leading newlines for source map and copyright comments

[jwilsson]

Which issue, if any, is this issue related to?

#2120

Is there anything in the PR that needs further explanation?

I opted for a regexp to check for any kind of whitespace so it will accept tabs as well. Let me know if you want tests for tabs too.

[jwilsson]

I've never worked with Jest before but when looking at the build failure, I'm guessing I need to update the snapshots for it?

[jeddy3]

I'm guessing I need to update the snapshots for it?

The jest snapshots changes look good:

Object {
             "column": 3,
    -        "line": 1,
    -        "rule": "comment-whitespace-inside",
    -        "severity": "error",
    -        "text": "Expected whitespace after "/*" (comment-whitespace-inside)",
    -      },

i.e. we are loosing one comment-whitespace-inside warning at 1:3. This is correct as the top of the 001 stylesheet looks like so:

/*!
 * Bootstrap v4.0.0-alpha.5 (https://getbootstrap.com)
 * Copyright 2011-2016 The Bootstrap Authors
 * Copyright 2011-2016 Twitter, Inc.
 * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
 */
/*! normalize.css v4.2.0 | MIT License | github.com/necolas/normalize.css */

Where the bootstrap copyright was erroneously triggering a warning (and the normalise one was not)

@jwilsson Yep, press u at the interactive menu (npm run jest -- --watch) to update the snapshot, and then commit&push the changes.

[jwilsson]

@jeddy3 Cool, thanks for the explanation!

Snapshots are updated.

[davidtheclark]

Thanks @jwilsson!

[davidtheclark]

Added note to changelog:

• Fixed: comment-whitespace-inside no longer complains about /*! comments with non-space whitespace (e.g. newlines) (#2121)