Sniffing from STDIN shows Generic.Files.LowercasedFilename.NotFound error

[skyrpex]

Atom's PHPCS linter plugin uses now STDIN to lint on the fly. Someone that uses the Wordpress-VIP ruleset is getting this error Generic.Files.LowercasedFilename.NotFound.

The output of this command cat "path/myfile.php" | phpcs --report=json --standard=WordPress-VIP is:

{
    "totals": {
        "errors": 1,
        "warnings": 0,
        "fixable": 0
    },
    "files": {
        "STDIN": {
            "errors": 1,
            "warnings": 0,
            "messages": [
                {
                    "message": "Filename \"STDIN\" doesn't match the expected filename \"stdin\"",
                    "source": "Generic.Files.LowercasedFilename.NotFound",
                    "severity": 5,
                    "type": "ERROR",
                    "line": 1,
                    "column": 1,
                    "fixable": false
                }
            ]
        }
    }
}

You'll notice that STDIN is treated the filename... See AtomLinter/linter-phpcs#60

[gsherwood]

The proper way to resolve this is for the plugin to tell PHPCS the filename so that sniffs that check the filename still work correctly. To do that, the first line of the input should be phpcs_input_file: [file path], for example:

phpcs_input_file: /path/to/test.php
<?php
echo 'test';

[gsherwood]

I've posted the same comment on the linked issue for the plugin. This feature was added in version 2.0 specifically to allow for plugin (Sublime plugins, at the time) to support filename checking.

[gsherwood]

Now that I've said that, the quick and easy way to fix this is for the sniff to ignore files with the name STDIN, which I'll also do. But that's something that will need to wait for the next release while the Atom plugin could be updated to work correctly today.