yake 0.5.2 → 0.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 05423d5da13bfc7484b2cf3f8a0a5c71534480b9925183b813bb8bdbaf564b1d
-  data.tar.gz: 2ff53556d45a9dec3b909c4e711da615652127c9ce48f60516910944d44c3542
+  metadata.gz: f2cf5c971016a9089087501bca0a31862c9f2f9ffdd586e2dfb965a190a664da
+  data.tar.gz: 8eaab803ca82cb0610f8775753e3cc2f1c472833417ff7db3940f0813a3561d0
 SHA512:
-  metadata.gz: 8b467a4358d9d73b603e16470b737a0a3c9bed0f9a14246ec035fe6cf99dba694d621d72d517e6959b8a5788fbc7a6fad72e6630fcf817fd1ca1f606e5558d78
-  data.tar.gz: c9648172bae6dde99fad24d063670766d9722f428c51cc5e6e3aac034fb86050a1f5db17aae1d41243a6d6e368ff322076120a14da7926489eccc684ea907df7
+  metadata.gz: ecafe24268afd558fcd5bbf388d03f334112d8c272a1f49688121a70662186ccfbb706a2d96407b8bbc13870515e5f7907a2b267432387e71070aa9bd6d2da29
+  data.tar.gz: ae003774e4626ee4afc13fef2f0a480813fa91a4a03ba3d1a1480e5c5770a748d2c629949fdb07d6e3941cecfb2eb963276613082fbb7a1866105f4f4a831fd6

data/README.md

@@ -67,11 +67,11 @@ gem install yake
 
 So why use `yake` for your Lambda functions?
 
-#### Event Logging
+### Event Logging
 
 By default, the `handler` function wraps its block in log lines formatted to match the style of Amazon's native Lambda logs sent to CloudWatch. Each invocation of the handler will log both the _input event_ and the _returned value_, prefixed with the ID of the request:
 
-```
+```plaintext
 START RequestId: 149c500f-028a-4b57-8977-0ef568cf8caf Version: $LATEST
 INFO RequestId: 149c500f-028a-4b57-8977-0ef568cf8caf EVENT { … }
 …
@@ -101,7 +101,7 @@ Fizz.new.logger == Yake.logger
 # => true
 ```
 
-#### API Routes
+### API Routes
 
 A common use of Lambda functions is as a proxy for API Gateway. Oftentimes users will deploy a single Lambda function to handle all requests coming from API Gateway.
 
@@ -168,14 +168,14 @@ Route an event to one of the declared routes:
 ```ruby
 handler :lambda_handler do |event|
   route event
-rescue Yake::UndeclaredRoute => err
+rescue Yake::Errors::UndeclaredRoute => err
   respond 404, { message: err.message }.to_json
 rescue => err
   respond 500, { message: err.message }.to_json
 end
 ```
 
-#### Zero Dependencies
+### Zero Dependencies
 
 Finally, `yake` does not depend on any other gems, using the Ruby stdlib only. This helps keep your Lambda packages slim & speedy.
 
@@ -227,8 +227,13 @@ require 'yake/support'
 `String` transformations:
 
 ```ruby
+host = 'https://example.com/'
+path = '/path/to/resource'
+host / path
+# => "https://example.com/path/to/resource"
+
 'snake_case_string'.camel_case
-# => SnakeCaseString
+# => "SnakeCaseString"
 
 "Zml6eg==\n".decode64
 # => "fizz"
@@ -237,7 +242,7 @@ require 'yake/support'
 # => "Zml6eg==\n"
 
 'CamelCaseString'.snake_case
-# => 'camel_case_string'
+# => "camel_case_string"
 
 'Zml6eg=='.strict_decode64
 # => "fizz"
@@ -259,7 +264,7 @@ require 'yake/support'
 # => :SnakeCaseSymbol
 
 :CamelCaseSymbol.snake_case
-# => 'camel_case_symbol'
+# => :camel_case_symbol
 ```
 
 `UTC` Time helper

data/lib/yake/support.rb

@@ -5,6 +5,7 @@ require 'time'
 class Hash
   def encode64() to_json.encode64 end
   def strict_encode64() to_json.strict_encode64 end
+  def stringify_names() JSON.parse(to_json) end
   def symbolize_names() JSON.parse(to_json, symbolize_names: true) end
   def to_form() URI.encode_www_form(self) end
 end

data/lib/yake/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Yake
-  VERSION = '0.5.2'
+  VERSION = '0.5.3'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: yake
 version: !ruby/object:Gem::Version
-  version: 0.5.2
+  version: 0.5.3
 platform: ruby
 authors:
 - Alexander Mancevice
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-03-05 00:00:00.000000000 Z
+date: 2022-04-09 00:00:00.000000000 Z
 dependencies: []
 description:
 email: