From 5898911bfca6c2fca2133017c4cbd768131d4ca7 Mon Sep 17 00:00:00 2001
From: Eyas <eyas.sharaiha@gmail.com>
Date: Mon, 8 Jul 2024 12:03:56 -0400
Subject: [PATCH] Update MatTooltip's "message not present" test to use
 null/undefined types outright.

We were using nullness assertions to cause these assignments to succeed, but we should allow users to set null/undefined values outright.

Right now we don't, so this update will cause the tests to fail. But this will be soon fixed.
---
 src/material/tooltip/tooltip.spec.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/material/tooltip/tooltip.spec.ts b/src/material/tooltip/tooltip.spec.ts
index b61eb9479982..5569df953caa 100644
--- a/src/material/tooltip/tooltip.spec.ts
+++ b/src/material/tooltip/tooltip.spec.ts
@@ -413,12 +413,12 @@ describe('MDC-based MatTooltip', () => {
     it('should not show tooltip if message is not present or empty', () => {
       assertTooltipInstance(tooltipDirective, false);
 
-      tooltipDirective.message = undefined!;
+      tooltipDirective.message = undefined;
       fixture.detectChanges();
       tooltipDirective.show();
       assertTooltipInstance(tooltipDirective, false);
 
-      tooltipDirective.message = null!;
+      tooltipDirective.message = null;
       fixture.detectChanges();
       tooltipDirective.show();
       assertTooltipInstance(tooltipDirective, false);