From 6ad6eaa8731ec2c1516f3a1460a0db694b810502 Mon Sep 17 00:00:00 2001
From: Rob Parrett <robparrett@gmail.com>
Date: Fri, 11 Oct 2024 08:35:22 -0700
Subject: [PATCH] Fix `println` in `morph_targets` example (#15851)

# Objective

This example uses `println` from a system, which we don't advise people
do. It also gives no context for the debug prints, which I assumed to be
stray debug code at first.

## Solution

Use `info!`, and add a small amount of context so the console output
looks deliberate.

## Testing

`cargo run --example morph_targets`
---
 examples/animation/morph_targets.rs | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/examples/animation/morph_targets.rs b/examples/animation/morph_targets.rs
index 7d5e26047c34a..258059bf55655 100644
--- a/examples/animation/morph_targets.rs
+++ b/examples/animation/morph_targets.rs
@@ -103,8 +103,10 @@ fn name_morphs(
     let Some(names) = mesh.morph_target_names() else {
         return;
     };
+
+    info!("Target names:");
     for name in names {
-        println!("  {name}");
+        info!("  {name}");
     }
     *has_printed = true;
 }