routes-analyzer 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e0df5dfa530f0ff7771563a035f35bd225a1b7d20e01c87aa626c87fa60a94a4
-  data.tar.gz: 1683d8d3a06202ce56e266bdd20b0d8805a08fc9eac68d9041be507fe78b367a
+  metadata.gz: d59454435cfcca8978b29560a38ecd2457cdfd1ac6486be5a71fa9c9b24ea443
+  data.tar.gz: 9c15d8ccb50eb9a2acc1a70c525deede37594200aca4b2bc1f08f9ab857a36ec
 SHA512:
-  metadata.gz: ddec876f42e606cca4f39b24ff3c2d442ae1d4ec635de8e6abba2434be1ca22629abe98a24750c048559ce67de9ec7c6042bb8481f8a87790508fcda5e28165d
-  data.tar.gz: 867674e3c3c49f0ed810d78b6871092261b815e5f6fe696de450973cadd9de6dd8ecdf7e759af0867245a8a2e92bba5612657f0f623110744d4db72dd5ea3f0e
+  metadata.gz: a85f24d238c05674ae36a97c30f36aa2d2913c77d53a2907c39a99203c2c1d77e93f86533c8cbbcbad7abbf0b56835e468906e04548075d609a0716ac42132bd
+  data.tar.gz: bded888809fdda525cf230a50a9bad7fce9e705716d325257f931f2882524a10e6338d46ec820e1cb67e5c9f674ec89011cfde4ea19283edce0795fba943448e

data/README.md

@@ -1,5 +1,7 @@
 # Routes::Analyzer
 
+[![Gem Version](https://badge.fury.io/rb/routes-analyzer.svg)](https://badge.fury.io/rb/routes-analyzer)
+
 A Ruby on Rails plugin that tracks and analyzes route usage in your application. It uses Redis to store route access patterns and provides insights into which routes are being used and which are not.
 
 ## Features
@@ -109,12 +111,26 @@ Displays current configuration and tests Redis connectivity.
 ## How It Works
 
 1. **Middleware Integration**: The plugin automatically adds middleware to your Rails application
-2. **Request Tracking**: Each HTTP request is analyzed to extract route information
-3. **Redis Storage**: Usage data is stored in Redis with the following structure:
+2. **Route Filtering**: Only routes explicitly defined in `routes.rb` are tracked. This ensures that:
+   - Undefined routes (404 errors) are not tracked
+   - Catch-all routes that handle unknown paths don't pollute the data
+   - Only legitimate application routes are analyzed
+3. **Request Tracking**: Each valid HTTP request is analyzed to extract route information
+4. **Redis Storage**: Usage data is stored in Redis with the following structure:
    - Route path and HTTP method
    - Access count within the timeframe
    - Last access timestamp
-4. **Data Expiration**: Redis keys automatically expire after the configured timeframe plus a buffer period
+5. **Data Expiration**: Redis keys automatically expire after the configured timeframe plus a buffer period
+
+## Route Detection
+
+The middleware uses Rails' routing system to determine if a route is valid:
+
+- **Path Parameters Check**: Verifies that Rails recognized the route and set path parameters
+- **Route Recognition**: Uses `Rails.application.routes.recognize_path` to confirm the route exists in `routes.rb`
+- **Error Handling**: Gracefully handles routing errors and invalid requests without tracking them
+
+This approach ensures that only routes you've intentionally defined are included in the usage analysis.
 
 ## Data Structure
 

data/lib/routes/analyzer/middleware.rb

@@ -23,6 +23,9 @@ module Routes
         return false unless Routes::Analyzer.track_usage?
         return false unless env["action_controller.instance"]
 
+        # Check if the route is actually defined in routes.rb
+        return false unless route_defined_in_rails?(env)
+
         true
       rescue => e
         Rails.logger.warn "Routes::Analyzer: Failed to check tracking conditions: #{e.message}"
@@ -57,6 +60,32 @@ module Routes
         Rails.logger.warn "Routes::Analyzer: Failed to track route usage: #{e.message}"
       end
 
+      def route_defined_in_rails?(env)
+        request = Rack::Request.new(env)
+
+        # First check: if Rails didn't set path_parameters, it means the route wasn't recognized
+        # This happens when Rails can't match the request to any defined route
+        path_params = env["action_dispatch.request.path_parameters"]
+        return false unless path_params
+
+        # Second check: verify that Rails can recognize this path/method combination
+        # This ensures the route is actually defined in routes.rb and not just handled by a catch-all
+        route_exists = Rails.application.routes.recognize_path(
+          request.path_info,
+          method: request.request_method.downcase.to_sym
+        )
+
+        return true if route_exists
+        false
+      rescue ActionController::RoutingError, NoMethodError
+        # If recognize_path raises RoutingError, the route is not defined in routes.rb
+        # NoMethodError can occur if the controller/action doesn't exist
+        false
+      rescue => e
+        Rails.logger.warn "Routes::Analyzer: Error checking route definition: #{e.message}"
+        false
+      end
+
       def extract_route_info(env, request)
         # Get the matched route from Rails
         if env["action_controller.instance"]

data/lib/routes/analyzer/version.rb

@@ -1,5 +1,5 @@
 module Routes
   module Analyzer
-    VERSION = "0.1.1"
+    VERSION = "0.1.2"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: routes-analyzer
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Gregorio Galante