railwatch 0.3.6 → 0.4.0

data/lib/railwatch.rb

@@ -599,6 +599,28 @@ module Railwatch
     File.expand_path("../db/#{database}_migrate", __dir__)
   end
 
+  # The one browser client, relative to the gem root. The dashboard bundle
+  # is built from it, the install generator copies it, the gem ships it (the
+  # only app/frontend file it does), and a host with its own frontend build
+  # (Railwatch Cloud) imports it from browser_client_path.
+  BROWSER_CLIENT = "app/frontend/lib/railwatch.ts"
+
+  def self.browser_client_path
+    File.expand_path("../#{BROWSER_CLIENT}", __dir__)
+  end
+
+  # One realistic wire record per record type, exactly as the gem's own
+  # subscribers emit it, generated by spec/railwatch/wire_fixtures_spec.rb.
+  # A receiver tests its mapper against these instead of hand-writing what
+  # it thinks the gem sends.
+  def self.wire_fixtures_path
+    File.expand_path("../lib/railwatch/wire_fixtures.json", __dir__)
+  end
+
+  def self.wire_fixtures
+    @wire_fixtures ||= JSON.parse(File.read(wire_fixtures_path)).freeze
+  end
+
   # Raised when the engine's models are used in an app whose database.yml
   # has no entry for them. They must never fall back to the host's primary
   # connection: the telemetry tables are unprefixed (`sessions`, `visits`,

data/lib/tasks/railwatch_tasks.rake

@@ -612,3 +612,10 @@ namespace :railwatch do
     res.is_a?(Net::HTTPSuccess) ? puts("Deploy #{deploy} recorded") : abort("Deploy failed: #{res.code} #{res.body}")
   end
 end
+
+namespace :railwatch do
+  desc "Regenerate lib/railwatch/wire_fixtures.json from the gem's own subscribers"
+  task :wire_fixtures do
+    sh({ "RAILWATCH_WRITE_WIRE_FIXTURES" => "1" }, "bundle exec rspec spec/railwatch/wire_fixtures_spec.rb -e 'matches the shipped'")
+  end
+end