| Index: pkg/analysis_server/test/integration/search/get_type_hierarchy_test.dart
|
| diff --git a/pkg/analysis_server/test/integration/search/get_type_hierarchy_test.dart b/pkg/analysis_server/test/integration/search/get_type_hierarchy_test.dart
|
| index 1793c6f834268948effe3daf8323598e67c62cc8..7849b7592acf0916769feeaf3208565547d3a055 100644
|
| --- a/pkg/analysis_server/test/integration/search/get_type_hierarchy_test.dart
|
| +++ b/pkg/analysis_server/test/integration/search/get_type_hierarchy_test.dart
|
| @@ -269,14 +269,6 @@ main /* target */ () {
|
| offset)).then((result) {
|
| if (result.hierarchyItems == null) {
|
| return null;
|
| - } else if (result.hierarchyItems.isEmpty) {
|
| - // TODO(paulberry): As a result of bug 21230, a type hierarchy result
|
| - // with no hierarchyItems field gets misinterpreted as a type hierarchy
|
| - // result with a hierarchyItems which is an empty list. To work around
|
| - // that, treat an empty hierarchyItems list as equivalent to
|
| - // hierarchyItems being absent. Once bug 21230 is fixed we should
|
| - // remove this.
|
| - return null;
|
| } else {
|
| return new HierarchyResults(result.hierarchyItems);
|
| }
|
|
|