log_method 1.0.0.pre.beta1 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bc351505c3fb62a69bc4f0f98a31335a212026dcec15f8644d7a0265bece1d16
-  data.tar.gz: 825b0e8dd2243d002e1c2c792e3e3f1b70b780b95d9719d236779e99327bc675
+  metadata.gz: aaf9e766e7cd25359757ba13ccb52a0f21452c835025dde17e58a2ec1591c311
+  data.tar.gz: ec61724f38c1f35ce76747cd5f3b9f21c0f775b76e4bfd43bcf76d8cf01c9318
 SHA512:
-  metadata.gz: 5ee91a5b361300c00b7fe13d2ff87a7722e54031ddd20c3c16365c940155f8870444485f51ab0406926bea062c3afb19ab2932f9f9b15159798e2687a814e216
-  data.tar.gz: 82e25bef7a840a873aae5e0e1afce8bd92d8f4dfa4831479dabe7ebd67f45919f5bf81ac28212ec54949a4522fef7a00a15210a70f33b46aa7cc97b5998a60ac
+  metadata.gz: b6d1a643280ce11e2502d364da9d15c1f9032eb0b7ed81f8c70cc2431fe1113a9a8c05447e1590e308271705ea3db5a5d847982281e4e9a6c99caae06a3abe73
+  data.tar.gz: cca740859bfed322dc5762b7190b743bdcff095f12d82a9541c9e27544243a4c90295b5d16f5f0116cf68d09dd17a3e393a25c530240329b54cc9c2c020d9769

data/README.md

@@ -36,24 +36,20 @@ class SomeClass
 end
 ```
 
-Assuming you have configured trace ids and current user id (see below for how), this is what your log message will look like (assuming the id of `some_active_record` is 42):
+Assuming you have configured trace ids and current user id (see below for how), this is what your log message will look like (assuming the id of `current_user` is 42 and that `some_active_record` is a `Widget` with id 7889):
 
 ```
-[SomeClass#some_method](via LogMethod::Log) trace_id:7efa5401-08d8-44e3-b101-d5806563a3da current_user_id:42 [User:7889]: Beginnging the operation
+[SomeClass#some_method](via LogMethod::Log) trace_id:7efa5401-08d8-44e3-b101-d5806563a3da current_user_id:42 [Widget:7889]: Beginnging the operation
 ```
 
 Let's break down each part and understand why it's there, which will help you understand why you should use this gem:
 
-* `[SomeClass#some_method]` - this gives the class and method where the log statement originated. Super helpful when looking at log output and
-trying to find what code generated that log message.
-* `(via LogMethod::Log)` - This makes it clear that *this* gem produced this output. If you don't see this, it means something else is generating
-log output, too.  Very handy for understanding the source of your log statements.
-* `trace_id:7efa5401-08d8-44e3-b101-d5806563a3da` - If you set a trace id at the start of a web request, or when you queue a background job, you
-can then trace all log statements related to that request. SUPER handy for understanding what all happened in a given request you are looking at.
-* `current_user_id:42` - System behavior often depends on who is logged in or who the "current actor" is. So you want this in your log.
-* `[SomeActiveRecord:7889]:` - Almost always, code is operating on some object or operating in the context of some object.  It's nice to know
-exactly which one.
-* `Beginnging the operation` - And, of course, your log message
+* `[SomeClass#some_method]`                        -  this gives the class and method where the log statement originated. Super helpful when looking at log output and trying to find what code generated that log message.
+* `(via LogMethod::Log)`                           -  This makes it clear that *this* gem produced this output. If you don't see this, it means something else is generating log output, too.  Very handy for understanding the source of your log statements.
+* `trace_id:7efa5401-08d8-44e3-b101-d5806563a3da`  -  If you set a trace id at the start of a web request, or when you queue a background job, you can then trace all log statements related to that request. SUPER handy for understanding what all happened in a given request you are looking at.
+* `current_user_id:42`                             -  System behavior often depends on who is logged in or who the "current actor" is. So you want this in your log.
+* `[Widget:7889]:`                                 -  Code is almost always operating on some object or operating in the context of some object.  It's nice to know exactly which one.
+* `Beginnging the operation`                       -  And, of course, your log message
 
 ### `log` method, explained
 

data/lib/log_method/version.rb

@@ -1,3 +1,3 @@
 module LogMethod
-  VERSION="1.0.0-beta1"
+  VERSION="1.0.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: log_method
 version: !ruby/object:Gem::Version
-  version: 1.0.0.pre.beta1
+  version: 1.0.0
 platform: ruby
 authors:
 - Dave Copeland
-autorequire:
+autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-10-24 00:00:00.000000000 Z
+date: 2021-11-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -38,7 +38,7 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-description:
+description: 
 email:
 - davec@naildrivin5.com
 executables: []
@@ -73,7 +73,7 @@ metadata:
   homepage_uri: https://github.com/sustainable-rails/log_method
   source_code_uri: https://github.com/sustainable-rails/log_method
   changelog_uri: https://github.com/sustainable-rails/log_method/releases
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -84,12 +84,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.5.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
-rubygems_version: 3.2.29
-signing_key:
+rubygems_version: 3.0.3
+signing_key: 
 specification_version: 4
 summary: A nice log method for your Rails app that provides a ton of useful context
   in each message!