RubyMine 2024.2 'Method could be private' quick-fix inserts visibility at nearest declaration in modules

Quick-Fix Insertion Logic

In RubyMine 2024.2, the "Method could be private" quick-fix determines the insertion point by placing the visibility keyword (private or protected) at the nearest preceding visibility declaration. If the module contains no explicit visibility sections, the IDE inserts the keyword directly above the flagged method. Because Ruby visibility modifiers apply to all subsequent method definitions in the file, this action effectively converts all methods defined after the insertion point to that visibility level.

Configuration and Constraints

Currently, there are no project-level settings or configuration options to:

• Restrict the intention action to class files only.
• Require an existing private block before allowing the insertion.
• Prevent the modification of subsequent methods in the same file.

Safe Workflow for Shared Modules

Because the inspection's call-graph analysis is performed per-class rather than per-module, a method may be flagged as "could be private" based on one including class, while remaining essential for public access in another. To avoid introducing NoMethodError or unintentionally hiding public methods, follow this workflow:

1. Verify All Callers: Use Alt+F7 (Find Usages) on the method to identify every class that includes the module and calls the method. Do not rely solely on the inspection flag.
2. Manual Visibility Sections: Instead of using the Alt+Enter quick-fix, manually create a private section at the bottom of the module and move the method definition there.
3. Validate Scope: If the method must remain public for some includers but is only used privately by others, it must remain public.
4. Refresh Analysis: If you have recently refactored the module's inclusion hierarchy, go to File > Invalidate Caches... to ensure the inspection is not operating on stale data.

Verification Step

To confirm the impact of a quick-fix in your specific module structure, apply the fix to a test method and check the visibility of all methods defined below it using the RubyMine structure tool window (Alt+7 / Cmd+7).