Remain compatible with new translation format to be introduced in Elixir 1.19

Author: Alex Martsinovich

lib/sentry/logger_handler.ex

@@ -360,6 +360,16 @@ defmodule Sentry.LoggerHandler do
     end
   end
 
+  # Elixir 1.19 puts string translation inside the report instead of replacing
+  # it completely. We switch it back for compatibility with existing code.
+  defp log_unfiltered(
+         %{msg: {:report, %{elixir_translation: unicode_chardata}}} = log_event,
+         sentry_opts,
+         %__MODULE__{} = config
+       ) do
+    log_unfiltered(%{log_event | msg: {:string, unicode_chardata}}, sentry_opts, config)
+  end
+
   # A string was logged. We check for the :crash_reason metadata and try to build a sensible
   # report from there, otherwise we use the logged string directly.
   defp log_unfiltered(

test/sentry/logger_handler_test.exs

@@ -154,7 +154,7 @@ defmodule Sentry.LoggerHandlerTest do
       assert %KeyError{} = event.original_exception
       assert [exception] = event.exception
       assert exception.type == "KeyError"
-      assert exception.value == "key :foo not found in: []"
+      assert exception.value == "key :foo not found in:\n\n    []"
       assert Enum.find(exception.stacktrace.frames, &(&1.function =~ "Keyword.fetch!/2"))
     end
   end
@@ -286,7 +286,7 @@ defmodule Sentry.LoggerHandlerTest do
       assert %KeyError{} = event.original_exception
       assert [exception] = event.exception
       assert exception.type == "KeyError"
-      assert exception.value == "key :foo not found in: []"
+      assert exception.value == "key :foo not found in:\n\n    []"
       assert Enum.find(exception.stacktrace.frames, &(&1.function =~ "Keyword.fetch!/2"))
     end