activeerror 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7152e2ef6d0ce997ab2c1ac6ad20301641bc3888da16d14d8ba447f0f25bbe42
-  data.tar.gz: c75638bb627a0bc6250e3eb7fd2c0041dda4eb7b1ac6849de0d2bda07cd7663d
+  metadata.gz: 4a975ff9c639f582045df2fe349d69c5359b6060c0421f8c08e8c9e5a8578fcc
+  data.tar.gz: acbed4f63bd84ee096c225df7fbd693ed74586ae3813ca3c9c0b7e067ac5078d
 SHA512:
-  metadata.gz: 2576054be5ff1b83af55777b9135a991e6fe05a845c1197d55aad43b79676fb830a09712be37c0d7591f1eb7f5e36b09af7ad8c71cf3a129f32a9d985dd3fb5d
-  data.tar.gz: 81ff00bc1f0e4e0fbe9230ec37e0fb72b1bc960375f9c64c9c6348fff2ec6ca2d8f98b237dec00b9e02fadbd4a7eee9b3427d2aea486f5c747ed06b479df0f9c
+  metadata.gz: b2d918aba97dea878b9f11e0bce25ea478c76ceb7aee9a479dcdb327c93aae3debde34af92e04cfc27ca8402993dd792e96782a770b21288809f0fe447bdf092
+  data.tar.gz: a82cd81c6b60217ac2a483d19e48f6ba02794b15028e0254e10a30b1e03a9f8304510c564a9d7a16e95bdc461e25f7d9c6994f5f089fb882ac36270244823c4c

data/README.md

@@ -2,8 +2,8 @@
 
 One of the fundemental tools needed to take your Rails app to production is a
 way to track errors that are triggered. Unfortunately, theres no free, easy,
-open source way to track them for small or medium apps. Honeybadger and Sentry are great,
-but they are only free for a single user and are closed source. With Sentry
+open source way to track them for small or medium apps. Honeybadger, Sentry, 
+and AppSignal are great, but they are are closed source. With Sentry
 looking at using your data as training
 data([link](https://blog.sentry.io/ai-privacy-and-terms-of-service-updates/?original_referrer=https%3A%2F%2Fsentry.io%2F))
 there should be an easy open source alternative where you control the data.
@@ -16,7 +16,7 @@ with is the one baked into Rails that we use everyday in development. So with
 ActiveError, when an error gets raised it's captured and stored in the
 database (we attempt to group the same error together as Instances to reduce
 noise) and then we recreate the error and display it using the built in debug
-view from Rails. Once you've resolved the error you can click "Resolve" with
+view from Rails. Once you've resolved the error you can click "Resolve" which
 will destroy the record.
 
 ![screenshot 1](https://github.com/npezza93/active_error/blob/main/.github/screenshot1.png)

data/app/models/active_error/fault.rb

@@ -13,15 +13,11 @@ module ActiveError
                     yaml: { unsafe_load: true }
 
     serialize :backtrace, type: Array, coder: YAML
-    serialize :backtrace_locations, type: Array, coder: YAML, 
+    serialize :backtrace_locations, type: Array, coder: YAML,
                                     yaml: { unsafe_load: true }
     serialize :blamed_files, type: Array, coder: YAML
 
-    scope :top_level, lambda {
-      left_joins(:parent_cause).where(
-        parent_causes_active_error_faults: { id: nil }
-      )
-    }
+    scope :top_level, -> { where.missing(:parent_cause) }
 
     def exception
       ExceptionMock.make(fault: self)

data/lib/active_error/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ActiveError
-  VERSION = Gem::Version.new("1.0.0")
+  VERSION = "1.0.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: activeerror
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Nick Pezza