alephant-logger-json 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 84eb3ae131800ea10978a1bef31ae0a51bde66c4
-  data.tar.gz: d7eda923aa0c8a7fb348840675f040185b6f295a
+  metadata.gz: 0154daa470efe5ef12b3e19a2bb11893cdf4b686
+  data.tar.gz: c5324b5beaef4b5becf02d4dcd7920d81ae7d154
 SHA512:
-  metadata.gz: 1941155f17fc7b8d0795a98550ed9ce743eaea9c84799cd78c00d8588b747a3ed241247c070390469be85148c276df0e6936391e18d91343287287a6c6174eac
-  data.tar.gz: 16962fa4fc1344968f6ed9546d921e38effe01a6fb375bdbdfa17ed40ffd13c4a406fa4075d66c7cf4ddffbe965f2a9346537d79d583f3c919d066f66beb9637
+  metadata.gz: 219d526f9be1c043f4c83978178c4552f0f950fd0df109bcc675885dc9aa67ff1f4e7f25d581a619cdaca9ce8170cf440ef87972ef13470cb6cb2979bea025be
+  data.tar.gz: fddbc2a85c4d059daf439a8724999e4c048dd9a1f048eda9b82fb1cf7f22bf9fde40c1cba4d09b2a06e7891c58b69f840067097196cdf6abf0fce2afe6a33aad

data/Rakefile

@@ -1,2 +1,4 @@
 require "bundler/gem_tasks"
+require "rake/rspec"
 
+task :default => :spec

data/alephant-logger-json.gemspec

@@ -1,15 +1,15 @@
 # coding: utf-8
 lib = File.expand_path('../lib', __FILE__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'alephant/logger/json/version'
+require "alephant/logger/json/version"
 
 Gem::Specification.new do |spec|
   spec.name          = "alephant-logger-json"
   spec.version       = Alephant::Logger::JSON::VERSION
   spec.authors       = ["Dan Arnould"]
   spec.email         = ["dan@arnould.co.uk"]
-  spec.summary       = %q{alephant-logger driver enabling structured logging in JSON}
-  spec.description   = %q{alephant-logger driver enabling structured logging in JSON}
+  spec.summary       = "alephant-logger driver enabling structured logging in JSON"
+  spec.description   = "alephant-logger driver enabling structured logging in JSON"
   spec.homepage      = ""
   spec.license       = "MIT"
 
@@ -21,4 +21,6 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "bundler", "~> 1.7"
   spec.add_development_dependency "rake", "~> 10.0"
   spec.add_development_dependency "rspec", "~> 3"
+  spec.add_development_dependency "rspec-nc"
+  spec.add_development_dependency "rake-rspec"
 end

data/lib/alephant/logger/json/version.rb

@@ -1,7 +1,7 @@
 module Alephant
   module Logger
     class JSON
-      VERSION = "0.1.0"
+      VERSION = "0.1.1"
     end
   end
 end

data/lib/alephant/logger/json.rb

@@ -9,24 +9,20 @@ module Alephant
         @nesting = options.fetch(:nesting, false)
       end
 
-      private
-
-      def flatten_values_to_s(hash)
-        Hash[hash.map { |k, v| [k, v.to_s] }]
-      end
-
-      public
-
       [:debug, :info, :warn, :error].each do |level|
         define_method(level) do |hash|
+          return if hash.is_a? String
           hash["level"] = level.to_s
-
-          hash = flatten_values_to_s hash if not @nesting
-
+          hash = flatten_values_to_s hash unless @nesting
           @log_file.write(::JSON.generate(hash) + "\n")
         end
       end
+
+      private
+
+      def flatten_values_to_s(hash)
+        Hash[hash.map { |k, v| [k, v.to_s] }]
+      end
     end
   end
 end
-

data/spec/alephant/logger/json_spec.rb

@@ -1,5 +1,4 @@
 require "spec_helper"
-
 require "alephant/logger/json"
 
 describe Alephant::Logger::JSON do
@@ -12,7 +11,7 @@ describe Alephant::Logger::JSON do
 
   before do
     allow(File).to receive(:open) { log_file }
-    allow(log_file).to receive :sync= 
+    allow(log_file).to receive :sync=
   end
 
   shared_examples "JSON logging" do
@@ -61,7 +60,16 @@ describe Alephant::Logger::JSON do
     end
   end
 
-  %w[debug info warn error].each do |level|
+  shared_examples "gracefully fail with string arg" do
+    let(:log_message) { "Unable to connect to server" }
+
+    specify { expect(log_file).not_to receive(:write) }
+    specify do
+      expect { subject.debug log_message }.not_to raise_error
+    end
+  end
+
+  %w(debug info warn error).each do |level|
     describe "##{level}" do
       let(:level) { level }
 
@@ -69,6 +77,8 @@ describe Alephant::Logger::JSON do
 
       it_behaves_like "nests flattened to strings"
 
+      it_behaves_like "gracefully fail with string arg"
+
       context "with nesting allowed" do
         subject do
           described_class.new(log_path, :nesting => true)
@@ -79,4 +89,3 @@ describe Alephant::Logger::JSON do
     end
   end
 end
-

data/spec/spec_helper.rb

@@ -1,89 +1,9 @@
-# This file was generated by the `rspec --init` command. Conventionally, all
-# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
-# The generated `.rspec` file contains `--require spec_helper` which will cause this
-# file to always be loaded, without a need to explicitly require it in any files.
-#
-# Given that it is always loaded, you are encouraged to keep this file as
-# light-weight as possible. Requiring heavyweight dependencies from this file
-# will add to the boot time of your test suite on EVERY test run, even for an
-# individual file that may not need all of that loaded. Instead, consider making
-# a separate helper file that requires the additional dependencies and performs
-# the additional setup, and require it from the spec files that actually need it.
-#
-# The `.rspec` file also contains a few flags that are not defaults but that
-# users commonly want.
-#
-# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
 RSpec.configure do |config|
-  # rspec-expectations config goes here. You can use an alternate
-  # assertion/expectation library such as wrong or the stdlib/minitest
-  # assertions if you prefer.
   config.expect_with :rspec do |expectations|
-    # This option will default to `true` in RSpec 4. It makes the `description`
-    # and `failure_message` of custom matchers include text for helper methods
-    # defined using `chain`, e.g.:
-    # be_bigger_than(2).and_smaller_than(4).description
-    #   # => "be bigger than 2 and smaller than 4"
-    # ...rather than:
-    #   # => "be bigger than 2"
     expectations.include_chain_clauses_in_custom_matcher_descriptions = true
   end
 
-  # rspec-mocks config goes here. You can use an alternate test double
-  # library (such as bogus or mocha) by changing the `mock_with` option here.
   config.mock_with :rspec do |mocks|
-    # Prevents you from mocking or stubbing a method that does not exist on
-    # a real object. This is generally recommended, and will default to
-    # `true` in RSpec 4.
     mocks.verify_partial_doubles = true
   end
-
-# The settings below are suggested to provide a good initial experience
-# with RSpec, but feel free to customize to your heart's content.
-=begin
-  # These two settings work together to allow you to limit a spec run
-  # to individual examples or groups you care about by tagging them with
-  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
-  # get run.
-  config.filter_run :focus
-  config.run_all_when_everything_filtered = true
-
-  # Limits the available syntax to the non-monkey patched syntax that is recommended.
-  # For more details, see:
-  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
-  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
-  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
-  config.disable_monkey_patching!
-
-  # This setting enables warnings. It's recommended, but in some cases may
-  # be too noisy due to issues in dependencies.
-  config.warnings = true
-
-  # Many RSpec users commonly either run the entire suite or an individual
-  # file, and it's useful to allow more verbose output when running an
-  # individual spec file.
-  if config.files_to_run.one?
-    # Use the documentation formatter for detailed output,
-    # unless a formatter has already been configured
-    # (e.g. via a command-line flag).
-    config.default_formatter = 'doc'
-  end
-
-  # Print the 10 slowest examples and example groups at the
-  # end of the spec run, to help surface which specs are running
-  # particularly slow.
-  config.profile_examples = 10
-
-  # Run specs in random order to surface order dependencies. If you find an
-  # order dependency and want to debug it, you can fix the order by providing
-  # the seed, which is printed after each run.
-  #     --seed 1234
-  config.order = :random
-
-  # Seed global randomization in this process using the `--seed` CLI option.
-  # Setting this allows you to use `--seed` to deterministically reproduce
-  # test failures related to randomization by passing the same `--seed` value
-  # as the one that triggered the failure.
-  Kernel.srand config.seed
-=end
 end

metadata

@@ -1,57 +1,85 @@
 --- !ruby/object:Gem::Specification
 name: alephant-logger-json
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Dan Arnould
-autorequire:
+autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-04-19 00:00:00.000000000 Z
+date: 2015-07-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
+  name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
         version: '1.7'
-  name: bundler
-  prerelease: false
   type: :development
+  prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
         version: '1.7'
 - !ruby/object:Gem::Dependency
+  name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
         version: '10.0'
-  name: rake
-  prerelease: false
   type: :development
+  prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
         version: '10.0'
 - !ruby/object:Gem::Dependency
+  name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
         version: '3'
-  name: rspec
-  prerelease: false
   type: :development
+  prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
         version: '3'
+- !ruby/object:Gem::Dependency
+  name: rspec-nc
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rake-rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 description: alephant-logger driver enabling structured logging in JSON
 email:
 - dan@arnould.co.uk
@@ -74,7 +102,7 @@ homepage: ''
 licenses:
 - MIT
 metadata: {}
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -89,9 +117,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project:
-rubygems_version: 2.1.9
-signing_key:
+rubyforge_project: 
+rubygems_version: 2.0.14
+signing_key: 
 specification_version: 4
 summary: alephant-logger driver enabling structured logging in JSON
 test_files: