Remove unused loader argument from Plugin initializer #2095
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.
I've been working on adding Puma instrumentation to our internal metrics gem. By reading the plugin code I got it to work in a way we want (no configuration required to enable the plugin from the gem) but I noticed I had to pass a slightly confusing
loader
argument when initializing the plugin.In the current version of the gem, strangely enough the
Plugin
class is passed as loader, while it happens inside thePluginLoader
class:puma/lib/puma/plugin.rb
Line 13 in b646fc5
this seems to have been an error made during refactoring in 33e0fa9 as the original implementation made more sense:
puma/lib/puma/plugin_loader.rb
Line 11 in 663666c
but even at that time, it seems the loader argument was never used, hence this PR removing it.
While technically part of the plugins API:
puma/docs/plugins.md
Lines 37 to 38 in 6bb070b
this does not affect the documented
Puma::Plugin.create do ... end
way of doing things.Your checklist for this pull request
[changelog skip]
the pull request title.[ci skip]
to the title of the PR.#issue
" to the PR description or my commit messages.