{"action":"created","issue":{"url":"https://api.github.com/repos/flutter/flutter/issues/8783","repository_url":"https://api.github.com/repos/flutter/flutter","labels_url":"https://api.github.com/repos/flutter/flutter/issues/8783/labels{/name}","comments_url":"https://api.github.com/repos/flutter/flutter/issues/8783/comments","events_url":"https://api.github.com/repos/flutter/flutter/issues/8783/events","html_url":"https://github.com/flutter/flutter/issues/8783","id":214318572,"number":8783,"title":"Clean up: Remove ignore of strong mode down cast composite warnings in analysis options","user":{"login":"kasperl","id":2156198,"avatar_url":"https://avatars2.githubusercontent.com/u/2156198?v=3","gravatar_id":"","url":"https://api.github.com/users/kasperl","html_url":"https://github.com/kasperl","followers_url":"https://api.github.com/users/kasperl/followers","following_url":"https://api.github.com/users/kasperl/following{/other_user}","gists_url":"https://api.github.com/users/kasperl/gists{/gist_id}","starred_url":"https://api.github.com/users/kasperl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kasperl/subscriptions","organizations_url":"https://api.github.com/users/kasperl/orgs","repos_url":"https://api.github.com/users/kasperl/repos","events_url":"https://api.github.com/users/kasperl/events{/privacy}","received_events_url":"https://api.github.com/users/kasperl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-15T08:39:37Z","updated_at":"2017-03-15T14:01:24Z","closed_at":null,"body":"Once 1.23.0-dev.6.0 lands as the embedded Dart SDK in Flutter, we should be able to remove the `strong_mode_down_cast_composite: ignore` lines from all the analysis options files. The new default is to only issue the warning if users opt into it by adding `strong_mode_down_cast_composite: warning` in their analysis options files -- which means that not mentioning anything in analysis options behaves the same as ignoring the warning. As such it is safe to keep the old `ignore` lines around, but it would be nice to clean it up.\r\n\r\nSee https://github.com/dart-lang/sdk/issues/28588."},"comment":{"url":"https://api.github.com/repos/flutter/flutter/issues/comments/286749958","html_url":"https://github.com/flutter/flutter/issues/8783#issuecomment-286749958","issue_url":"https://api.github.com/repos/flutter/flutter/issues/8783","id":286749958,"user":{"login":"eseidelGoogle","id":11857803,"avatar_url":"https://avatars1.githubusercontent.com/u/11857803?v=3","gravatar_id":"","url":"https://api.github.com/users/eseidelGoogle","html_url":"https://github.com/eseidelGoogle","followers_url":"https://api.github.com/users/eseidelGoogle/followers","following_url":"https://api.github.com/users/eseidelGoogle/following{/other_user}","gists_url":"https://api.github.com/users/eseidelGoogle/gists{/gist_id}","starred_url":"https://api.github.com/users/eseidelGoogle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eseidelGoogle/subscriptions","organizations_url":"https://api.github.com/users/eseidelGoogle/orgs","repos_url":"https://api.github.com/users/eseidelGoogle/repos","events_url":"https://api.github.com/users/eseidelGoogle/events{/privacy}","received_events_url":"https://api.github.com/users/eseidelGoogle/received_events","type":"User","site_admin":false},"created_at":"2017-03-15T14:01:24Z","updated_at":"2017-03-15T14:01:24Z","body":"So this should be possible to act on after our next Dart roll in the engine?"}}
{"actor":{"display_login":"eseidelGoogle"}}