Tools used by Dart's continuous integration (CI) testing that aren't needed by Dart SDK contributors. Mirrored from dart.googlesource.com/dart_ci. Do not land pull requests on Github.
BSD 3-Clause "New" or "Revised" License
18
stars
5
forks
source link
results feed cannot be migrated to null safety #141
The results feed is written using the open-source Angular Dart framework, and that framework has not been fully migrated to null-safety yet (the ngcomponents package of Material components is not migrated).
Until then, the results feed must be maintained by pinning its development to use version 2.10.0 stable of the Dart SDK and
pinning packages to their old versions.
It doesn't look like much progress is being made on open-source Angular Dart, so the most reasonable course seems to be
to keep the results feed as-is, and not attempt a migration.
As a long-term project, the results feed should be migrated to Flutter. This should not be that hard, and the current_results_ui which is served along with the results feed is already written in Flutter web.
This is a low priority, but the issue is filed so that we can track any progress or decisions on this.
The results feed is written using the open-source Angular Dart framework, and that framework has not been fully migrated to null-safety yet (the ngcomponents package of Material components is not migrated).
Until then, the results feed must be maintained by pinning its development to use version 2.10.0 stable of the Dart SDK and pinning packages to their old versions.
It doesn't look like much progress is being made on open-source Angular Dart, so the most reasonable course seems to be to keep the results feed as-is, and not attempt a migration.
As a long-term project, the results feed should be migrated to Flutter. This should not be that hard, and the current_results_ui which is served along with the results feed is already written in Flutter web.
This is a low priority, but the issue is filed so that we can track any progress or decisions on this.