Fix to show the name of log type correctly in Ruby 3.4 #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Describe the change
This PR fixes an issue in Ruby 3.4 where TTY::Logger fails to display the correct log type name.
Why are we doing this?
Suppose we run the following code:
in Ruby 3.3.5:
✔ success Deployed successfullyin Ruby 3.4.1:
ℹ info Deployed successfullyThis is likely due to changes in the behavior of
Thread::Backtrace::Locationreturned bycaller_locations.https://github.com/ruby/ruby/blob/master/doc/NEWS/NEWS-3.4.0.md#compatibility-issues
Benefits
We can use TTY::Logger in Ruby 3.4.
Drawbacks
I hope nothing.
Requirements
masterbranch?