Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1179)

Issue 2622323002: Fix an analysis error in tests. (Closed)

Created:
3 years, 11 months ago by scheglov
Modified:
3 years, 11 months ago
Reviewers:
Paul Berry
CC:
reviews_dartlang.org
Target Ref:
refs/heads/master
Visibility:
Public.

Description

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M pkg/analyzer/test/generated/all_the_rest_test.dart View 1 chunk +1 line, -1 line 1 comment Download

Messages

Total messages: 4 (1 generated)
scheglov
3 years, 11 months ago (2017-01-11 17:22:04 UTC) #1
scheglov
Committed patchset #1 (id:1) manually as 41f8d695b0ab0e42e27426715121432cb4d08de1 (presubmit successful).
3 years, 11 months ago (2017-01-11 17:22:17 UTC) #3
Paul Berry
3 years, 11 months ago (2017-01-11 19:05:30 UTC) #4
Message was sent while issue was closed.
https://codereview.chromium.org/2622323002/diff/1/pkg/analyzer/test/generated...
File pkg/analyzer/test/generated/all_the_rest_test.dart (right):

https://codereview.chromium.org/2622323002/diff/1/pkg/analyzer/test/generated...
pkg/analyzer/test/generated/all_the_rest_test.dart:365: void
reset({List<List<String>> packages}) {
Consider adding an assertion, e.g.:

assert(packages == null);

Just so that no one tries to call this method and pass in packages.

Alternatively, consider creating a ResolverTestCase.resetWithPackages() method
that accepts the packages argument; that way ResolverTestCase.reset() can go
back to being a zero-argument function, and we can override it safely here.

Powered by Google App Engine
This is Rietveld 408576698