Fix SecurityController callback reference (v0.2.1) #4
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.
Fixes ArgumentError in production environments with eager loading
Problem
SecurityController was calling
skip_before_action :authenticate_api_keys_user!but the actual callback defined in ApplicationController is:authenticate_api_keys_owner!Solution
Fixed the callback reference to use the correct method name, aligning with the gem's owner-agnostic design.
Changes
Closes #2
Generated with Claude Code