Bob Nystrom
a80b71fc15
- "util.dart" is completely unused, so deleted. - We had two copies of "utils.dart" in two directories. It needs to exist in both places, but doesn't need to be copy/pasted. Replaced one with an export of the other. - Fixed bad import paths to "../utils.dart" in html/custom/ tests. These were causing those tests to crash DDC. (Now most are instead failing because of #31577, so it's not a *huge* improvement, but it's a step in the right direction.) - Don't use unittest in utils.dart. Change-Id: I28c432b53c992a5ec790f5804453cddb0f44cbe5 Reviewed-on: https://dart-review.googlesource.com/27301 Reviewed-by: Vijay Menon <vsm@google.com> Commit-Queue: Bob Nystrom <rnystrom@google.com>
15 lines
754 B
Dart
15 lines
754 B
Dart
/// The test runner for DDC does not handle tests that import files using
|
|
/// relative imports that reach outside of the directory containing the test
|
|
/// (i.e. "../" imports). Since tests both in this directory and in "custom/"
|
|
/// use utils.dart, it needs to be accessible from both places.
|
|
///
|
|
/// We could have every test outside of "custom/" import "custom/utils.dart",
|
|
/// but that feels weird since "utils.dart" doesn't have anything to do with
|
|
/// custom elements.
|
|
///
|
|
/// Instead, it lives there, but is exported from here for the tests in this
|
|
/// directory to import.
|
|
// TODO(rnystrom): If the DDC test runner is fixed to use a different module
|
|
// root that handles "../" imports, move "custom/utils.dart" to here.
|
|
export 'custom/utils.dart';
|