{"action":"created","issue":{"url":"https://api.github.com/repos/stylelint/stylelint/issues/978","repository_url":"https://api.github.com/repos/stylelint/stylelint","labels_url":"https://api.github.com/repos/stylelint/stylelint/issues/978/labels{/name}","comments_url":"https://api.github.com/repos/stylelint/stylelint/issues/978/comments","events_url":"https://api.github.com/repos/stylelint/stylelint/issues/978/events","html_url":"https://github.com/stylelint/stylelint/issues/978","id":143532597,"number":978,"title":"Warnings are logged multiple times on a single run","user":{"login":"declandewet","id":1918632,"avatar_url":"https://avatars.githubusercontent.com/u/1918632?v=3","gravatar_id":"","url":"https://api.github.com/users/declandewet","html_url":"https://github.com/declandewet","followers_url":"https://api.github.com/users/declandewet/followers","following_url":"https://api.github.com/users/declandewet/following{/other_user}","gists_url":"https://api.github.com/users/declandewet/gists{/gist_id}","starred_url":"https://api.github.com/users/declandewet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/declandewet/subscriptions","organizations_url":"https://api.github.com/users/declandewet/orgs","repos_url":"https://api.github.com/users/declandewet/repos","events_url":"https://api.github.com/users/declandewet/events{/privacy}","received_events_url":"https://api.github.com/users/declandewet/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-03-25T16:11:54Z","updated_at":"2016-03-28T09:04:18Z","closed_at":"2016-03-25T18:50:35Z","body":"#### Note:\r\n\r\nForgive me if I'm putting this in the wrong place - I'm unaware if this bug originates from `stylelint` or `postcss-reporter`.\r\n\r\n#### Bug Report:\r\n\r\n> Describe the issue. Is it a bug or a feature request (new rule, new option, etc.)?\r\n\r\nLinter warnings are reported multiple times for each file on a single run:\r\n\r\n![a screenshot of the problem](https://infinit.io/_/36c3JTe.png)\r\n\r\nI have set [postcss-reporter](https://github.com/postcss/postcss-reporter)'s `clearMessages` option to true, and tried `false` - the bug is consistent both times.\r\n\r\n> Which rule, if any, is this issue related to?\r\n\r\nNone.\r\n\r\n> What CSS is needed to reproduce this issue?\r\n\r\n```stylus\r\n.foo, .bar // to trigger newline rule\r\n  color: pink \r\n```\r\n\r\n> What stylelint configuration is needed to reproduce this issue?\r\n\r\n```json\r\n{\r\n  \"extends\": \"stylelint-config-standard\",\r\n  \"rules\": {\r\n    \"declaration-block-trailing-semicolon\": null\r\n  }\r\n}\r\n```\r\n\r\n> Which version of stylelint are you using?\r\n\r\n`5.2.0`\r\n\r\n> How are you running stylelint: CLI, PostCSS plugin, Node API?\r\n\r\nConsumed as a PostCSS plugin in the asset pipeline for [Roots](http://roots.cx). Example Roots config `app.coffee`:\r\n\r\n```coffeescript\r\nstylelint = require 'stylelint'\r\ncss_pipeline = require 'css-pipeline'\r\n\r\nmodule.exports =\r\n  postcss:\r\n    use: [stylelint]\r\n  extensions:\r\n    css_pipeline\r\n      files: 'assets/css/*.css'\r\n```\r\n\r\n> Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?\r\n\r\nYes, syntax is [SugarSS](https://github.com/postcss/sugarss), with [precss](https://github.com/jonathantneal/precss).\r\n\r\n> What did you expect to happen?\r\n\r\nWarnings should have only been reported once.\r\n\r\n> What actually happened (e.g. what warnings or errors you are getting)?\r\n\r\nWarnings were reported three times.\r\n"},"comment":{"url":"https://api.github.com/repos/stylelint/stylelint/issues/comments/202312620","html_url":"https://github.com/stylelint/stylelint/issues/978#issuecomment-202312620","issue_url":"https://api.github.com/repos/stylelint/stylelint/issues/978","id":202312620,"user":{"login":"declandewet","id":1918632,"avatar_url":"https://avatars.githubusercontent.com/u/1918632?v=3","gravatar_id":"","url":"https://api.github.com/users/declandewet","html_url":"https://github.com/declandewet","followers_url":"https://api.github.com/users/declandewet/followers","following_url":"https://api.github.com/users/declandewet/following{/other_user}","gists_url":"https://api.github.com/users/declandewet/gists{/gist_id}","starred_url":"https://api.github.com/users/declandewet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/declandewet/subscriptions","organizations_url":"https://api.github.com/users/declandewet/orgs","repos_url":"https://api.github.com/users/declandewet/repos","events_url":"https://api.github.com/users/declandewet/events{/privacy}","received_events_url":"https://api.github.com/users/declandewet/received_events","type":"User","site_admin":false},"created_at":"2016-03-28T09:04:18Z","updated_at":"2016-03-28T09:04:18Z","body":"> Have you found it [stylelint] to be broadly compatible with SugarSS? \r\n\r\nYes.\r\n\r\n> I see you're turning off the \"declaration-block-trailing-semicolon\". That makes sense. If that's the only rule that's incompatible with SugarSS then we should consider removing it from stylelint-config-standard.\r\n\r\nSo far, that's the only rule I've found to be incompatible with SugarSS. However, I don't think it should be removed from `stylelint-config-standard` - the SugarSS syntax isn't for everyone - and a lack of semicolons is invalid in regular css syntax. I think keeping things the way they are is fine - perhaps adding a note to the README regarding this rule and SugarSS is enough - I don't think the change is big enough to warrant a new standard config.\r\n\r\n> I see you're using stylelint as a PostCSS plugin (through Roots). Is that because using the PostCSS plugin is your preferred method, or because the SugarSS syntax isn't yet available when using the CLI or Node API?\r\n\r\nThe PostCSS way is the easiest to manage within the Roots stack, as Roots extensions and [Accord](http://github.com/jenius/accord) (the transpiler engine powering Roots) are first-class citizens of the setup (if that makes sense). While it's possible to use the Node API, it would be rather awkward. That being said:\r\n\r\n> Would you use either of these the CLI or Node API if a SugarSS syntax option was added?\r\n\r\nPersonally, I would not - but I do have a hunch other people might, so it might be worth exploring."}}