✨ Support Alternate Loggers

[pboling]

• e.g. https://github.com/pboling/activesupport-tagged_logging

Since Rails uses autoloading, there is no need to explicitly require active_support/tagged_logging, and doing so actively prevents using an alternative.

I have created a suite of gems that replace the Rails logger. They extract the logging tooling from Rails 8, add in some refactoring and fixes that allow broadcasting, tagged logging, and blocks, to all work together, (which bugs have always been present in tagged logging, and remain in v8.0, see Rails PR 53093 and Rails PR 53105).

It works with Rails because of the autoloading. If a namespace / constant is already defined, it won't go looking for it. So by defining it in my extracted gems, the vanilla (broken) Rails version doesn't load.

At that point the only problem comes from libraries which load certain Rails internals explicitly.

The suite of gems I'm aiming to have compatibility with is:

• Enhanced activesupport-logger which was ripped from Rails v8.0
• Enhanced activesupport-broadcast_logger which was ripped from Rails v8.0, and this PR
• Enhanced activesupport-tagged_logging which was ripped from Rails v8.0, and this PR

[santry]

Thanks @pboling!

[pboling]

Thanks! This was a good change, as, specifically TaggedLogging is one of the things Rails auto-loads...

But now I've discovered there are a few things that Rails loads explicitly, within active_support, that I'll need to work around. I was doing that in v1 of the suite, but didn't think I'd need to anymore, and I was wrong.

Anyways, this helps me get where I am going. Thanks again!

[pboling]

The latest release of the gem suite is now working with this change!

• https://github.com/pboling/activesupport-logger/releases/tag/v2.0.1
• https://github.com/pboling/activesupport-broadcast_logger/releases/tag/v2.0.1
• https://github.com/pboling/activesupport-tagged_logging/releases/tag/v2.0.1

[pboling]

Also, FWIW, this is related:
soutaro/steep#484

which mentions that active_support must be explicitly required according to: https://guides.rubyonrails.org/active_support_core_extensions.html

and which took the same approach of stopping the explicit require of active_support/tagged_logging, just like we did here.

So this was the right approach, and may have preemptively fixed the same bug that the steep project saw.