Update experimental_features with additional analyzer updates.
- Added running `dart pkg/analyzer/tool/api/generate.dart` to prevent
people from finding out they have to update the `api.txt` only when they
run try-jobs.
- We should also update
`pkg/analyzer_testing/lib/experiments/experiments.dart` at this point. I
always forget and spend time wondering why my tests aren't working. And
this is probably the most ideal step to do this at.
Change-Id: I68a33a39d7b5360e586f7aa17f223cf9d9014885
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/453644
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Auto-Submit: Kallen Tu <kallentu@google.com>
Commit-Queue: Kallen Tu <kallentu@google.com>
Reviewed-by: Nate Bosch <nbosch@google.com>
diff --git a/tools/experimental_features.yaml b/tools/experimental_features.yaml
index 71f47fa..640dda8 100644
--- a/tools/experimental_features.yaml
+++ b/tools/experimental_features.yaml
@@ -17,10 +17,14 @@
#
# analyzer:
# dart pkg/analyzer/tool/experiments/generate.dart
+# dart pkg/analyzer/tool/api/generate.dart
#
-# Also, pkg/analyzer/lib/src/dart/analysis/driver.dart will need a bump in
-# DATA_VERSION if making changes that change the "index" of any previous flags,
-# e.g. if adding a new flag that doesn't happen to be lexicographically last.
+# Bump DATA_VERSION in`pkg/analyzer/lib/src/dart/analysis/driver.dart` if making
+# changes that change the "index" of any previous flags, e.g. if adding a new
+# flag that doesn't happen to be lexicographically last.
+#
+# Update `pkg/analyzer_testing/lib/experiments/experiments.dart` to ensure that
+# the experiment is enabled for testing in the analyzer.
#
# kernel:
# dart pkg/front_end/tool/cfe.dart generate-experimental-flags
