cuba 3.6.0 → 3.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 42cd957e785c42b14bbfe58e527dacb30a01a6da
-  data.tar.gz: 9cea4d3fae0509433f694eb682429b5fef1e3224
+  metadata.gz: 5312bfcf95e9e0ac5e5a9d05fe883a4790ad768a
+  data.tar.gz: 8f96b48c062e5410dc50c467ba182edd0016d741
 SHA512:
-  metadata.gz: 84b6ac48a32e192b791840dfabf751293a1f11619f281c267dea76f94ec9be24e2ca0f67c555b8f2873e4e1958a616ff62d74185f8201d0cfe26122434afce8e
-  data.tar.gz: 61590ca736f30164a9f4546b21870e4bd3339f012c8484173cb4855c3115d0a7b896f92cc7e617031b975642bf09f0318305a1d0b784cac10bacdc5f209f3c4d
+  metadata.gz: 23057633a8adfe69110215e9ab6917f0d0b26b4fcebc6fdf5b0b7113936d31d16eb66e090f96ad7ef6aad22a63c8097c9eb52bacbee7e76ff02f12e4b8671652
+  data.tar.gz: f0babb7278078c7625e862cf5d78bda5f266d5f57b5de590842666fdf2e17dc199f6d15f86a56243601f7926be3a6c4e25b2d2bb8446d3d00cda4fd829dd5dfb

data/CHANGELOG

@@ -1,6 +1,10 @@
+3.7.0
+
+* Add syntactic sugar for matching all HTTP methods.
+
 3.6.0
 
-* Set Strict-Transport-Security to a better default
+* Set Strict-Transport-Security to a better default.
 
 3.5.0
 

data/README.md

@@ -30,16 +30,6 @@ It integrates many templates via [Tilt][tilt], and testing via
 [capybara]: http://github.com/jnicklas/capybara
 [rack-test]: https://github.com/brynary/rack-test
 
-Guide
------
-
-There's a book called [The Guide to Cuba][guide] that explains how
-to build web applications by following a minimalistic approach. It
-is recommended reading for anyone trying to learn the basics of
-Cuba and other related tools.
-
-[guide]: http://theguidetocuba.io
-
 Installation
 ------------
 
@@ -405,12 +395,13 @@ among your meta tags. Here's an example that assumes you are using
 HTTP Verbs
 ----------
 
-There are four matchers defined for HTTP Verbs: `get`, `post`, `put` and
-`delete`. But the world doesn't end there, does it? As you have the whole
-request available via the `req` object, you can query it with helper methods
-like `req.options?` or `req.head?`, or you can even go to a lower level
-and inspect the environment via the `env` object, and check for example if
-`env["REQUEST_METHOD"]` equals the obscure verb `PATCH`.
+There are matchers defined for the following HTTP Verbs: `get`,
+`post`, `put`, `patch`, `delete`, `head`, `options`, `link`, `unlink`
+and `trace`. As you have the whole request available via the `req`
+object, you can also query it with helper methods like `req.options?`
+or `req.head?`, or you can even go to a lower level and inspect the
+environment via the `env` object, and check for example if
+`env["REQUEST_METHOD"]` equals the verb `PATCH`.
 
 What follows is an example of different ways of saying the same thing:
 

data/cuba.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name              = "cuba"
-  s.version           = "3.6.0"
+  s.version           = "3.7.0"
   s.summary           = "Microframework for web applications."
   s.description       = "Cuba is a microframework for web applications."
   s.authors           = ["Michel Martens"]

data/lib/cuba.rb

@@ -325,10 +325,16 @@ class Cuba
   #
   #   on post, "signup" do
   #   end
-  def get;    req.get?    end
-  def post;   req.post?   end
-  def put;    req.put?    end
-  def delete; req.delete? end
+  def get;     req.get?     end
+  def post;    req.post?    end
+  def put;     req.put?     end
+  def patch;   req.patch?   end
+  def delete;  req.delete?  end
+  def head;    req.head?    end
+  def options; req.options? end
+  def link;    req.link?    end
+  def unlink;  req.unlink?  end
+  def trace;   req.trace?   end
 
   # If you want to halt the processing of an existing handler
   # and continue it via a different handler.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cuba
 version: !ruby/object:Gem::Version
-  version: 3.6.0
+  version: 3.7.0
 platform: ruby
 authors:
 - Michel Martens
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-03-19 00:00:00.000000000 Z
+date: 2016-06-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rack