{"action":"closed","issue":{"url":"https://api.github.com/repos/sass/sass-spec/issues/948","repository_url":"https://api.github.com/repos/sass/sass-spec","labels_url":"https://api.github.com/repos/sass/sass-spec/issues/948/labels{/name}","comments_url":"https://api.github.com/repos/sass/sass-spec/issues/948/comments","events_url":"https://api.github.com/repos/sass/sass-spec/issues/948/events","html_url":"https://github.com/sass/sass-spec/issues/948","id":183256506,"number":948,"title":"Add support for known failing specs","user":{"login":"nex3","id":188,"avatar_url":"https://avatars.githubusercontent.com/u/188?v=3","gravatar_id":"","url":"https://api.github.com/users/nex3","html_url":"https://github.com/nex3","followers_url":"https://api.github.com/users/nex3/followers","following_url":"https://api.github.com/users/nex3/following{/other_user}","gists_url":"https://api.github.com/users/nex3/gists{/gist_id}","starred_url":"https://api.github.com/users/nex3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nex3/subscriptions","organizations_url":"https://api.github.com/users/nex3/orgs","repos_url":"https://api.github.com/users/nex3/repos","events_url":"https://api.github.com/users/nex3/events{/privacy}","received_events_url":"https://api.github.com/users/nex3/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-10-16T08:55:00Z","updated_at":"2016-11-02T22:28:20Z","closed_at":"2016-11-02T22:28:20Z","body":"Right now, if a new implementation wanted to start the process of becoming sass-spec-compatible, there's no way to distinguish between a spec that's ignored for that implementation because it hasn't yet been implemented, or one that's ignored for some other reason (for example, #946). This makes it difficult to iteratively add support for more and more specs over time, while still running the passing specs to guard against any regressions.\n\nI suggest a per-implementation \"known failing\" status that asserts that a spec doesn't pass for some reason. I think it's probably better for it not to be explicit about the reason, since it will generally represent work that hasn't been done yet, where the distinction between incorrect output and an explicit error isn't relevant.\n"}}
{"actor":{"display_login":"nex3"}}