fix(Compiler): handle exception thrown by parsing an invalid micro ex…

…pression

While the error reported in #1502 was
fixed, the fix introduced a new, unhandled exception that would be reported as a
bug in the compiler given the same inputs.

PiperOrigin-RevId: 228791959

angular_ast/CHANGELOG.md

@@ -1,3 +1,6 @@
+*   Errors caused by parsing an invalid micro expression (i.e. `*ngFor`) are now
+    reported to the registered `ExceptionHandler` rather than thrown.
+
 ## 0.5.8
 
 *   Fixed a type error that occurred when recovering from a missing closing

angular_ast/lib/src/visitors/desugar_visitor.dart

@@ -174,10 +174,7 @@ class DesugarVisitor implements TemplateAstVisitor<TemplateAst, void> {
     astNode.bananas.clear();
   }
 
-  EmbeddedTemplateAst _desugarStar(
-    StandaloneTemplateAst astNode,
-    List<StarAst> stars,
-  ) {
+  TemplateAst _desugarStar(StandaloneTemplateAst astNode, List<StarAst> stars) {
     var starAst = stars[0];
     var origin = _toolFriendlyAstOrigin ? starAst : null;
     var starExpression = starAst.value?.trim();
@@ -201,11 +198,7 @@ class DesugarVisitor implements TemplateAstVisitor<TemplateAst, void> {
         );
       } catch (e) {
         exceptionHandler.handle(e);
-        if (astNode is EmbeddedTemplateAst) {
-          return astNode;
-        }
-        // We parsed this as something unexpected, and should not continue.
-        rethrow;
+        return astNode;
       }
       if (micro != null) {
         propertiesToAdd.addAll(micro.properties);