twiglet 3.2.1 → 3.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 64fa676db51b4a53f17a7f1ff578ba00b670c2df9100b6972f2cf4b6fb51c1fc
-  data.tar.gz: 014044c6cccb28d13d019a26715ad83a5532e38b5f4df7ecf9a9a211eaec6751
+  metadata.gz: 1b8119a5caed97ef5f329bfba3ebf1bd30a1d7f33db1b3e6908007f09facd2a0
+  data.tar.gz: c90de0a6b8cbc5e111f699cc9c0b1d9b0123d1e6745a7f3f93d0a3b8f52321a2
 SHA512:
-  metadata.gz: 3d771c2182011b62d5d5af36a55fb04069a2f19805733df475b2f8d0e93e9ccdffdbac81c24eda8ba2081950812b94f87673c931776b65a125fb973106ce1210
-  data.tar.gz: 01c66f316cabc1b1169d35ca224d2c35f5e79efab580df3c530deaddcf30f8b23a46549ffc46140540408fc8c60c916ea72cb1c67122d32233b633786c8289c8
+  metadata.gz: 94042f642ab02be62ec592691084df2445ea91c7ebccad768a270ef5b0c55e5d3152a935b8f21f1addd58e76f5b57192d864db2808262fd387969e2cfafc7d02
+  data.tar.gz: b050780d6193b3d69b2f5372bc2cf6870dd0ff139f42db12c2c7602f7ec5ecd5f810c71c8f77b7bdc0facfe3a5922d6de1a4733f64b8db1fe6a15a31e7327212

data/.github/workflows/dobby-actions.yml

@@ -9,7 +9,7 @@ jobs:
 
     steps:
       - name: bump version
-        uses: simplybusiness/dobby@v2.0.0
+        uses: simplybusiness/dobby@v2.1.0
         env:
           DOBBY_APP_ID: ${{ secrets.DOBBY_APP_ID }}
           DOBBY_PRIVATE_KEY: ${{ secrets.DOBBY_PRIVATE_KEY }}

data/.github/workflows/version-forget-me-not.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-18.04
 
     steps:
-      - uses: simplybusiness/version-forget-me-not@v2
+      - uses: simplybusiness/version-forget-me-not@V2.1.1
         env:
           ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           VERSION_FILE_PATH: "lib/twiglet/version.rb"

data/README.md

@@ -3,254 +3,4 @@ Like a log, only smaller.
 
 This library provides a minimal JSON logging interface suitable for use in (micro)services.  See the [RATIONALE](RATIONALE.md) for design rationale and an explantion of the Elastic Common Schema that we are using for log attribute naming.
 
-## Installation
-
-```bash
-gem install twiglet
-```
-
-## How to use
-
-### Instantiate the logger
-
-```ruby
-require 'twiglet/logger'
-logger = Twiglet::Logger.new('service name')
-```
-#### Optional initialization parameters
-A hash can optionally be passed in as a keyword argument for `default_properties`. This hash must be in the Elastic Common Schema format and will be present in every log message created by this Twiglet logger object.
-
-You may also provide an optional `output` keyword argument which should be an object with a `puts` method - like `$stdout`.
-
-In addition, you can provide another optional keyword argument called `now`, which should be a function returning a `Time` string in ISO8601 format.
-
-Lastly, you may provide the optional keyword argument `level` to initialize the logger with a severity threshold. Alternatively, the threshold can be updated at runtime by calling the `level` instance method.
-
-The defaults for both `output` and `now` should serve for most uses, though you may want to override them for testing as we have done [here](test/logger_test.rb).
-
-### Invoke the Logger
-
-```ruby
-logger.error({ event: { action: 'startup' }, message: "Emergency! There's an Emergency going on" })
-```
-
-This will write to STDOUT a JSON string:
-
-```json
-{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:54:59.164+01:00","log":{"level":"error"},"event":{"action":"startup"},"message":"Emergency! There's an Emergency going on"}
-```
-
-Obviously the timestamp will be different.
-
-Alternatively, if you just want to log some error string:
-
-```ruby
-logger.error("Emergency! There's an Emergency going on")
-```
-
-This will write to STDOUT a JSON string:
-
-```json
-{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:54:59.164+01:00","log":{"level":"error"}, "message":"Emergency! There's an Emergency going on"}
-```
-
-A message is always required unless a block is provided. The message can be an object or a string.
-
-#### Error logging
-An optional error can also be provided, in which case the error message and backtrace will be logged in the relevant ECS compliant fields:
-
-```ruby
-db_err = StandardError.new('Connection timed-out')
-logger.error({ message: 'DB connection failed.' }, db_err)
-
-# this is also valid
-logger.error('DB connection failed.', db_err)
-```
-
-These will both result in the same JSON string written to STDOUT:
-
-```json
-{"ecs":{"version":"1.5.0"},"@timestamp":"2020-08-21T15:44:37.890Z","service":{"name":"service name"},"log":{"level":"error"},"message":"DB connection failed.","error":{"message":"Connection timed-out"}}
-```
-
-#### Custom fields
-Log custom event-specific information simply as attributes in a hash:
-
-```ruby
-logger.info({
-  event: { action: 'HTTP request' },
-  message: 'GET /pets success',
-  trace: { id: '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb' },
-  http: {
-    request: { method: 'get' },
-    response: { status_code: 200 }
-  },
-  url: { path: '/pets' }
-})
-```
-
-This writes:
-
-```json
-{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:56:49.527+01:00","log":{"level":"info"},"event":{"action":"HTTP request"},"message":"GET /pets success","trace":{"id":"1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb"},"http":{"request":{"method":"get"},"response":{"status_code":200}},"url":{"path":"/pets"}}
-```
-
-Similar to error you can use string logging here as:
-
-```
-logger.info('GET /pets success')
-```
-
-This writes:
-
-```json
-{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:56:49.527+01:00","log":{"level":"info"}}
-```
-
-It may be that when making a series of logs that write information about a single event, you may want to avoid duplication by creating an event specific logger that includes the context:
-
-```ruby
-request_logger = logger.with({ event: { action: 'HTTP request'}, trace: { id: '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb' }})
-```
-
-This can be used like any other Logger instance:
-
-```ruby
-request_logger.error({
-    message: 'Error 500 in /pets/buy',
-    http: {
-        request: { method: 'post', 'url.path': '/pet/buy' },
-        response: { status_code: 500 }
-    }
-})
-```
-
-which will print:
-
-```json
-{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:58:30.780+01:00","log":{"level":"error"},"event":{"action":"HTTP request"},"trace":{"id":"126bb6fa-28a2-470f-b013-eefbf9182b2d"},"message":"Error 500 in /pets/buy","http":{"request":{"method":"post","url.path":"/pet/buy"},"response":{"status_code":500}}}
-```
-
-### Log formatting
-Some third party applications will allow you to optionally specify a [log formatter](https://ruby-doc.org/stdlib-2.4.0/libdoc/logger/rdoc/Logger/Formatter.html).
-Supplying a Twiglet log formatter will format those third party logs so that they are ECS compliant and have the same default parameters as your application's internal logs.
-
-To access the formatter:
-```ruby
-logger.formatter
-```
-
-### HTTP Request Logging
-Take a look at this sample [Rack application](examples/rack/example_rack_app.rb#L15) with an ECS compliant
-[request logger](/examples/rack/request_logger.rb) as a template when configuring your own request logging middleware with Twiglet.
-
-### Log format validation
-Twiglet allows for the configuration of a custom validation schema. The validation schema must be [JSON Schema](https://json-schema.org/) compliant. Any fields not explicitly included in the provided schema are permitted by default.
-
-For example, given the following JSON Schema:
-```ruby
-validation_schema = <<-JSON
-    {
-      "type": "object",
-      "required": ["pet"],
-      "properties": {
-        "pet": {
-          "type": "object",
-          "required": ["name", "best_boy_or_girl?"],
-          "properties": {
-            "name": {
-              "type": "string",
-              "minLength": 1
-            },
-            "good_boy?": {
-              "type": "boolean"
-            }
-          }
-        }
-      }
-    }
-JSON
-```
-
-The logger can be instantiated with the custom schema
-```ruby
-custom_logger = Twiglet::Logger.new('service name', validation_schema: validation_schema)
-```
-
-Compliant log messages will log as normal.
-```ruby
-# this is compliant
-custom_logger.debug(pet: { name: 'Davis', good_boy?: true })
-
-# the result
-{:ecs=>{:version=>"1.5.0"}, :@timestamp=>"2020-05-11T15:01:01.000Z", :service=>{:name=>"petshop"}, :log=>{:level=>"debug"}, :pet=>{:name=>"Davis", :good_boy?=>true}}
-```
-
-Non compliant messages will raise an error.
-```ruby
-begin
-  custom_logger.debug(pet: { name: 'Davis' })
-rescue JSON::Schema::ValidationError
-  # we forgot to specify that he's a good boy!
-  puts 'uh-oh'
-end
-```
-
-#### Customizing error responses
-Depending on the application, it may not be desirable for the logger to raise Runtime errors. Twiglet allows you to configure a custom response for handling validation errors.
-
-Configure error handling by writing a block
-```ruby
-logger.configure_validation_error_response do |error|
-  # validation error handling goes here
-  # for example:
-  {YOUR APPLICATION BUG TRACKING SERVICE}.notify_error(error)
-end
-
-```
-
-### Use of dotted keys (DEPRECATED)
-
-Writing nested json objects could be confusing. This library has a built-in feature to convert dotted keys into nested objects, so if you log like this:
-
-```ruby
-logger.info({
-    'event.action': 'HTTP request',
-    message: 'GET /pets success',
-    'trace.id': '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb',
-    'http.request.method': 'get',
-    'http.response.status_code': 200,
-    'url.path': '/pets'
-})
-```
-
-or mix between dotted keys and nested objects:
-
-```ruby
-logger.info({
-    'event.action': 'HTTP request',
-    message: 'GET /pets success',
-    trace: { id: '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb' },
-    'http.request.method': 'get',
-    'http.response.status_code': 200,
-    url: { path: '/pets' }
-})
-```
-
-Both cases would print out exact the same log item:
-
-```json
-{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:59:31.183+01:00","log":{"level":"info"},"event":{"action":"HTTP request"},"message":"GET /pets success","trace":{"id":"1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb"},"http":{"request":{"method":"get"},"response":{"status_code":200}},"url":{"path":"/pets"}}
-```
-
-## How to contribute
-
-First: Please read our project [Code of Conduct](../CODE_OF_CONDUCT.md).
-
-Second: run the tests and make sure your changes don't break anything:
-
-```bash
-bundle exec rake test
-```
-
-Then please feel free to submit a PR.
+See [Full docs](docs/index.md)

data/{RATIONALE.md → docs/RATIONALE.md}

@@ -87,4 +87,4 @@ Please see the [code of conduct](CODE_OF_CONDUCT.md) for further info.
 
 # License
 
-This work is licensed under the MIT license - see the [LICENSE](LICENSE) file for further details.
+This work is licensed under the MIT license - see the [LICENSE](../LICENSE) file for further details.

data/docs/index.md

@@ -0,0 +1,256 @@
+# Twiglet: Ruby version
+Like a log, only smaller.
+
+This library provides a minimal JSON logging interface suitable for use in (micro)services.  See the [RATIONALE](docs/RATIONALE.md) for design rationale and an explantion of the Elastic Common Schema that we are using for log attribute naming.
+
+## Installation
+
+```bash
+gem install twiglet
+```
+
+## How to use
+
+### Instantiate the logger
+
+```ruby
+require 'twiglet/logger'
+logger = Twiglet::Logger.new('service name')
+```
+#### Optional initialization parameters
+A hash can optionally be passed in as a keyword argument for `default_properties`. This hash must be in the Elastic Common Schema format and will be present in every log message created by this Twiglet logger object.
+
+You may also provide an optional `output` keyword argument which should be an object with a `puts` method - like `$stdout`.
+
+In addition, you can provide another optional keyword argument called `now`, which should be a function returning a `Time` string in ISO8601 format.
+
+Lastly, you may provide the optional keyword argument `level` to initialize the logger with a severity threshold. Alternatively, the threshold can be updated at runtime by calling the `level` instance method.
+
+The defaults for both `output` and `now` should serve for most uses, though you may want to override them for testing as we have done [here](test/logger_test.rb).
+
+### Invoke the Logger
+
+```ruby
+logger.error({ event: { action: 'startup' }, message: "Emergency! There's an Emergency going on" })
+```
+
+This will write to STDOUT a JSON string:
+
+```json
+{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:54:59.164+01:00","log":{"level":"error"},"event":{"action":"startup"},"message":"Emergency! There's an Emergency going on"}
+```
+
+Obviously the timestamp will be different.
+
+Alternatively, if you just want to log some error string:
+
+```ruby
+logger.error("Emergency! There's an Emergency going on")
+```
+
+This will write to STDOUT a JSON string:
+
+```json
+{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:54:59.164+01:00","log":{"level":"error"}, "message":"Emergency! There's an Emergency going on"}
+```
+
+A message is always required unless a block is provided. The message can be an object or a string.
+
+#### Error logging
+An optional error can also be provided, in which case the error message and backtrace will be logged in the relevant ECS compliant fields:
+
+```ruby
+db_err = StandardError.new('Connection timed-out')
+logger.error({ message: 'DB connection failed.' }, db_err)
+
+# this is also valid
+logger.error('DB connection failed.', db_err)
+```
+
+These will both result in the same JSON string written to STDOUT:
+
+```json
+{"ecs":{"version":"1.5.0"},"@timestamp":"2020-08-21T15:44:37.890Z","service":{"name":"service name"},"log":{"level":"error"},"message":"DB connection failed.","error":{"message":"Connection timed-out"}}
+```
+
+#### Custom fields
+Log custom event-specific information simply as attributes in a hash:
+
+```ruby
+logger.info({
+  event: { action: 'HTTP request' },
+  message: 'GET /pets success',
+  trace: { id: '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb' },
+  http: {
+    request: { method: 'get' },
+    response: { status_code: 200 }
+  },
+  url: { path: '/pets' }
+})
+```
+
+This writes:
+
+```json
+{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:56:49.527+01:00","log":{"level":"info"},"event":{"action":"HTTP request"},"message":"GET /pets success","trace":{"id":"1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb"},"http":{"request":{"method":"get"},"response":{"status_code":200}},"url":{"path":"/pets"}}
+```
+
+Similar to error you can use string logging here as:
+
+```
+logger.info('GET /pets success')
+```
+
+This writes:
+
+```json
+{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:56:49.527+01:00","log":{"level":"info"}}
+```
+
+It may be that when making a series of logs that write information about a single event, you may want to avoid duplication by creating an event specific logger that includes the context:
+
+```ruby
+request_logger = logger.with({ event: { action: 'HTTP request'}, trace: { id: '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb' }})
+```
+
+This can be used like any other Logger instance:
+
+```ruby
+request_logger.error({
+    message: 'Error 500 in /pets/buy',
+    http: {
+        request: { method: 'post', 'url.path': '/pet/buy' },
+        response: { status_code: 500 }
+    }
+})
+```
+
+which will print:
+
+```json
+{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:58:30.780+01:00","log":{"level":"error"},"event":{"action":"HTTP request"},"trace":{"id":"126bb6fa-28a2-470f-b013-eefbf9182b2d"},"message":"Error 500 in /pets/buy","http":{"request":{"method":"post","url.path":"/pet/buy"},"response":{"status_code":500}}}
+```
+
+### Log formatting
+Some third party applications will allow you to optionally specify a [log formatter](https://ruby-doc.org/stdlib-2.4.0/libdoc/logger/rdoc/Logger/Formatter.html).
+Supplying a Twiglet log formatter will format those third party logs so that they are ECS compliant and have the same default parameters as your application's internal logs.
+
+To access the formatter:
+```ruby
+logger.formatter
+```
+
+### HTTP Request Logging
+Take a look at this sample [Rack application](examples/rack/example_rack_app.rb#L15) with an ECS compliant
+[request logger](/examples/rack/request_logger.rb) as a template when configuring your own request logging middleware with Twiglet.
+
+### Log format validation
+Twiglet allows for the configuration of a custom validation schema. The validation schema must be [JSON Schema](https://json-schema.org/) compliant. Any fields not explicitly included in the provided schema are permitted by default.
+
+For example, given the following JSON Schema:
+```ruby
+validation_schema = <<-JSON
+    {
+      "type": "object",
+      "required": ["pet"],
+      "properties": {
+        "pet": {
+          "type": "object",
+          "required": ["name", "best_boy_or_girl?"],
+          "properties": {
+            "name": {
+              "type": "string",
+              "minLength": 1
+            },
+            "good_boy?": {
+              "type": "boolean"
+            }
+          }
+        }
+      }
+    }
+JSON
+```
+
+The logger can be instantiated with the custom schema
+```ruby
+custom_logger = Twiglet::Logger.new('service name', validation_schema: validation_schema)
+```
+
+Compliant log messages will log as normal.
+```ruby
+# this is compliant
+custom_logger.debug(pet: { name: 'Davis', good_boy?: true })
+
+# the result
+{:ecs=>{:version=>"1.5.0"}, :@timestamp=>"2020-05-11T15:01:01.000Z", :service=>{:name=>"petshop"}, :log=>{:level=>"debug"}, :pet=>{:name=>"Davis", :good_boy?=>true}}
+```
+
+Non compliant messages will raise an error.
+```ruby
+begin
+  custom_logger.debug(pet: { name: 'Davis' })
+rescue JSON::Schema::ValidationError
+  # we forgot to specify that he's a good boy!
+  puts 'uh-oh'
+end
+```
+
+#### Customizing error responses
+Depending on the application, it may not be desirable for the logger to raise Runtime errors. Twiglet allows you to configure a custom response for handling validation errors.
+
+Configure error handling by writing a block
+```ruby
+logger.configure_validation_error_response do |error|
+  # validation error handling goes here
+  # for example:
+  {YOUR APPLICATION BUG TRACKING SERVICE}.notify_error(error)
+end
+
+```
+
+### Use of dotted keys (DEPRECATED)
+
+Writing nested json objects could be confusing. This library has a built-in feature to convert dotted keys into nested objects, so if you log like this:
+
+```ruby
+logger.info({
+    'event.action': 'HTTP request',
+    message: 'GET /pets success',
+    'trace.id': '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb',
+    'http.request.method': 'get',
+    'http.response.status_code': 200,
+    'url.path': '/pets'
+})
+```
+
+or mix between dotted keys and nested objects:
+
+```ruby
+logger.info({
+    'event.action': 'HTTP request',
+    message: 'GET /pets success',
+    trace: { id: '1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb' },
+    'http.request.method': 'get',
+    'http.response.status_code': 200,
+    url: { path: '/pets' }
+})
+```
+
+Both cases would print out exact the same log item:
+
+```json
+{"service":{"name":"service name"},"@timestamp":"2020-05-14T10:59:31.183+01:00","log":{"level":"info"},"event":{"action":"HTTP request"},"message":"GET /pets success","trace":{"id":"1c8a5fb2-fecd-44d8-92a4-449eb2ce4dcb"},"http":{"request":{"method":"get"},"response":{"status_code":200}},"url":{"path":"/pets"}}
+```
+
+## How to contribute
+
+First: Please read our project [Code of Conduct](../CODE_OF_CONDUCT.md).
+
+Second: run the tests and make sure your changes don't break anything:
+
+```bash
+bundle exec rake test
+```
+
+Then please feel free to submit a PR.

data/examples/rack/request_logger_test.rb

@@ -65,12 +65,12 @@ describe RequestLogger do
   end
 
   it 'logs an error message when a request is bad' do
-    -> { bad_request.get("/some/path") }.must_raise StandardError
+    expect { bad_request.get("/some/path") }.must_raise StandardError
     log = JSON.parse(output.string)
     assert_equal log['log']['level'], 'error'
     assert_equal log['error']['message'], 'some exception'
     assert_equal log['error']['type'], 'StandardError'
-    assert_includes log['error']['stack_trace'], 'request_logger_test.rb'
+    assert_includes log['error']['stack_trace'].first, 'examples/rack/request_logger_test.rb'
   end
 end
 

data/lib/hash_extensions.rb

@@ -24,6 +24,6 @@ module HashExtensions
     key.to_s
        .split('.')
        .reverse
-       .reduce(val) { |nested, key_part| Hash[key_part.to_sym, nested] }
+       .reduce(val) { |nested, key_part| { key_part.to_sym => nested } }
   end
 end

data/lib/twiglet/logger.rb

@@ -21,7 +21,7 @@ module Twiglet
 
       now = args.fetch(:now, -> { Time.now.utc })
       output = args.fetch(:output, $stdout)
-      level = args.fetch(:level, Logger::DEBUG)
+      level = args.fetch(:level, DEBUG)
       validation_schema = args.fetch(:validation_schema, File.read("#{__dir__}/validation_schema.json"))
 
       raise 'Service name is mandatory' \
@@ -70,7 +70,7 @@ module Twiglet
     private
 
     def add_stack_trace(hash_to_add_to, error)
-      hash_to_add_to[:error][:stack_trace] = error.backtrace.join("\n") if error.backtrace
+      hash_to_add_to[:error][:stack_trace] = error.backtrace if error.backtrace
     end
   end
 end

data/lib/twiglet/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Twiglet
-  VERSION = '3.2.1'
+  VERSION = '3.3.2'
 end

data/mkdocs.yml

@@ -0,0 +1,8 @@
+site_name: 'Twiglet Docs'
+nav:
+  - Home: index.md
+  - Code of Conduct: CODE_OF_CONDUCT.md
+  - "Why Twiglet?": RATIONALE.md
+
+plugins:
+  - techdocs-core

data/test/logger_test.rb

@@ -217,7 +217,7 @@ describe Twiglet::Logger do
       assert_equal 'Artificially raised exception', actual_log[:message]
       assert_equal 'divided by 0', actual_log[:error][:message]
       assert_equal 'ZeroDivisionError', actual_log[:error][:type]
-      assert_match 'logger_test.rb', actual_log[:error][:stack_trace].lines.first
+      assert_match 'test/logger_test.rb', actual_log[:error][:stack_trace].first
     end
 
     it 'should log an error without backtrace' do
@@ -357,6 +357,17 @@ describe Twiglet::Logger do
     it 'initializes the logger with the provided level' do
       assert_equal Logger::WARN, Twiglet::Logger.new('petshop', level: :warn).level
     end
+
+    it 'does not log lower level' do
+      logger = Twiglet::Logger.new(
+        'petshop',
+        now: @now,
+        output: @buffer,
+        level: Logger::INFO
+      )
+      logger.debug({ name: 'Davis', best_boy_or_girl?: true, species: 'dog' })
+      assert_empty @buffer.read
+    end
   end
 
   describe 'configuring error response' do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: twiglet
 version: !ruby/object:Gem::Version
-  version: 3.2.1
+  version: 3.3.2
 platform: ruby
 authors:
 - Simply Business
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-02-17 00:00:00.000000000 Z
+date: 2021-06-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json-schema
@@ -96,14 +96,15 @@ files:
 - ".gitignore"
 - ".rubocop.yml"
 - ".ruby-version"
-- CODE_OF_CONDUCT.md
 - Dockerfile
 - Gemfile
 - LICENSE
 - Makefile
-- RATIONALE.md
 - README.md
 - Rakefile
+- docs/CODE_OF_CONDUCT.md
+- docs/RATIONALE.md
+- docs/index.md
 - example_app.rb
 - examples/rack/example_rack_app.rb
 - examples/rack/request_logger.rb
@@ -115,6 +116,7 @@ files:
 - lib/twiglet/validation_schema.json
 - lib/twiglet/validator.rb
 - lib/twiglet/version.rb
+- mkdocs.yml
 - test/formatter_test.rb
 - test/hash_extensions_test.rb
 - test/logger_test.rb
@@ -141,7 +143,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.3
+rubygems_version: 3.2.15
 signing_key: 
 specification_version: 4
 summary: Twiglet