{"action":"created","issue":{"url":"https://api.github.com/repos/stylelint/stylelint/issues/1135","repository_url":"https://api.github.com/repos/stylelint/stylelint","labels_url":"https://api.github.com/repos/stylelint/stylelint/issues/1135/labels{/name}","comments_url":"https://api.github.com/repos/stylelint/stylelint/issues/1135/comments","events_url":"https://api.github.com/repos/stylelint/stylelint/issues/1135/events","html_url":"https://github.com/stylelint/stylelint/pull/1135","id":150935611,"number":1135,"title":"Ignore non-standard syntax in function-url-quote","user":{"login":"evilebottnawi","id":4567934,"avatar_url":"https://avatars.githubusercontent.com/u/4567934?v=3","gravatar_id":"","url":"https://api.github.com/users/evilebottnawi","html_url":"https://github.com/evilebottnawi","followers_url":"https://api.github.com/users/evilebottnawi/followers","following_url":"https://api.github.com/users/evilebottnawi/following{/other_user}","gists_url":"https://api.github.com/users/evilebottnawi/gists{/gist_id}","starred_url":"https://api.github.com/users/evilebottnawi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evilebottnawi/subscriptions","organizations_url":"https://api.github.com/users/evilebottnawi/orgs","repos_url":"https://api.github.com/users/evilebottnawi/repos","events_url":"https://api.github.com/users/evilebottnawi/events{/privacy}","received_events_url":"https://api.github.com/users/evilebottnawi/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/stylelint/stylelint/labels/PR:%20needs%20revision","name":"PR: needs revision","color":"B20C00"},{"url":"https://api.github.com/repos/stylelint/stylelint/labels/PR:%20review%20needed","name":"PR: review needed","color":"FFE600"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2016-04-25T17:46:52Z","updated_at":"2016-04-28T11:12:30Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/stylelint/stylelint/pulls/1135","html_url":"https://github.com/stylelint/stylelint/pull/1135","diff_url":"https://github.com/stylelint/stylelint/pull/1135.diff","patch_url":"https://github.com/stylelint/stylelint/pull/1135.patch"},"body":"https://github.com/stylelint/stylelint/issues/1133\r\nMaybe `hasVariable` move to utils. Also we can better process all inside `url` function throw `postcss-value-parser`(ignore all word contain variable), I first tried to write exactly, but `postcss-value-parser` handling very bad word contain url(`http://some-domain.com`, return some word - [\"http:\",\"/\", \"/\", \"some-domain\"] and etc). I do not know whether it is right, maybe not. If we change logic in `postcss-value-parser` we can change rule for ignore all variable and rule will work containing variable inside."},"comment":{"url":"https://api.github.com/repos/stylelint/stylelint/issues/comments/215391339","html_url":"https://github.com/stylelint/stylelint/pull/1135#issuecomment-215391339","issue_url":"https://api.github.com/repos/stylelint/stylelint/issues/1135","id":215391339,"user":{"login":"ntwb","id":1016458,"avatar_url":"https://avatars.githubusercontent.com/u/1016458?v=3","gravatar_id":"","url":"https://api.github.com/users/ntwb","html_url":"https://github.com/ntwb","followers_url":"https://api.github.com/users/ntwb/followers","following_url":"https://api.github.com/users/ntwb/following{/other_user}","gists_url":"https://api.github.com/users/ntwb/gists{/gist_id}","starred_url":"https://api.github.com/users/ntwb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ntwb/subscriptions","organizations_url":"https://api.github.com/users/ntwb/orgs","repos_url":"https://api.github.com/users/ntwb/repos","events_url":"https://api.github.com/users/ntwb/events{/privacy}","received_events_url":"https://api.github.com/users/ntwb/received_events","type":"User","site_admin":false},"created_at":"2016-04-28T11:12:30Z","updated_at":"2016-04-28T11:12:30Z","body":"Interesting discussion, and from someone who has had little time to contribute these past couple of weeks the pace at which this repo goes forward is breathtaking. This can be a good thing, or it can be a bad thing depending on how you look at it. People sometime need time to relax ☺️, explore other projects :octocat:, spend time with family 👪 , go away for the weekend ⛺ , have a drink 🍺etc \r\n\r\nFrom my WordPress background, backward compatibility is a pretty big thing, it also involves a great deal of technical debt, WordPress has be it good or bad backward compatibility going back  5,7, 9, 10, 12 years even. If breaking backward compatibility can be avoided then it is avoided, for better or worse, but that's a discussion for elsewhere, not here.\r\n\r\nTo that avail, I'd hate to see SCSS and Less syntaxes pulled from stylelint now, they are in, they are working reasonably well IMHO and I've been working with a SCSS project this past couple of weeks and have hit upon very few issues, if I had I would have created new stylelint issues here about those issues.\r\n\r\nSo, what I was thinking might best be explained using _milestones_, how about stylelint starts to use _milestones_ and use _multiple milestones_ at that,  `CSS`, `SCSS`, `Less` milestones. This way new features, code refactoring, performance testing for CSS could all happen in a `CSS` milestone. Once the current `CSS` milestone is completed then work on the `SCSS` milestone, then the `Less` milestone, and then start again back on the next/future `CSS` milestone. If there are SCSS or Less issues whilst working on the CSS milestone then the workaround for those issues is to disable the applicable rule/s until the issues can be addressed in the next _non-standard syntax_ milestone."}}