delivery-sdk-ruby 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6cc5777ca1aad7843166ac84a6af661c21882b20a00d21f93710bf1a06cae304
-  data.tar.gz: 140f1c745d5d38fd59448ff856e2203c2ba5c3c3ad37fc91cfc6410e5d666dba
+  metadata.gz: 5935e3de30556622cdc1d6c9ba309ea22120e0c17e79d0b0f72f22d75ba85619
+  data.tar.gz: 78c3a84a4c97a324b1cee12065f6a0b441b44d200054a0cd2df3d1f1d992f2cf
 SHA512:
-  metadata.gz: c9e45bca4d8dd901a849428ae90a4e3d28e38c06e859f48ffe481dda7fb0960f4dc79569d47368f3e0840052f02339f69aa1bd903db40e5d0a11bc09ff676318
-  data.tar.gz: 9e7e6ee1db6304034f39ed67935ea068d48dbcd1878c9d76a3fe17df5c30d3659f84f8e2ae817112377c850f5b868dec045693dc4da7976fa71773706c69a227
+  metadata.gz: bbb47f64b96aacb9b892833288972e108377b991c9fcf14faf1b1a48f529ac737ad8c73130abc5e9391cec67a53f332e0f82c2bc5827b276196433f014194653
+  data.tar.gz: abe85df664b4f113b60cf84727953cf99db8d14ee7aa88557b372a1f78f4fa875fb148278b3969a9d27960f3ab108d741da14451604e1da4d97b97bcf49dee08

data/README.md

@@ -51,7 +51,7 @@ You will use `KenticoCloud::Delivery::DeliveryClient` to obtain content from Ken
 delivery_client = KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>'
 ```
 
-**Pro tip:** You can alias namespaces to make them shorter, e.g.
+:gem: **Pro tip:** You can alias namespaces to make them shorter, e.g.
 
 ```ruby
 KC = KenticoCloud::Delivery
@@ -64,7 +64,7 @@ To enable [preview](https://developer.kenticocloud.com/docs/previewing-content-i
 
 ```ruby
 delivery_client = KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                               preview_key: '<your-preview-key>'
+                                                             preview_key: '<your-preview-key>'
 ```
 
 This enables preview, but you can toggle preview at any time by setting the `use_preview` attribute of DeliveryClient which is propogated to all queries created by the client, _or_ per-query by setting it's `use_preview` attribute:
@@ -87,7 +87,7 @@ If you've [secured access](https://developer.kenticocloud.com/docs/securing-publ
 
 ```ruby
 KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                             secure_key: '<your-secure-key>'
+                                           secure_key: '<your-secure-key>'
 ```
 
 ## Listing items
@@ -330,7 +330,7 @@ delivery_client.taxonomy('personas').execute do |response|
 end
 ```
 
-## Retreiveing content type elements
+## Retrieving content type elements
 
 Kentico Cloud provides an [endpoint](https://developer.kenticocloud.com/v1/reference#view-a-content-type-element) for obtaining details about a specific element of a content type. In the Ruby SDK, you can use the `.element` method:
 
@@ -342,7 +342,7 @@ end
 
 This returns a `KenticoCloud::Delivery::Responses::DeliveryElementResponse` where the `element` attribute is a dynamic OStruct representation of the JSON response. This means that you can access any property of the element by simply typing the name as in the above example.
 
-The element will always contain __codename__, __type__, and __name__, but multiple choice elements will also contain __options__ and taxonomy elements will contain __taxonomy_group__.
+The element will always contain __codename__, __type__, and __name__, but multiple choice elements will also contain __options__ and taxonomy elements will contain __taxonomy_group__. The Ruby SDK fully supports obtaining [custom elements](https://developer.kenticocloud.com/v1/reference#custom-elements-api) using this approach and any other methods.
 
 ## Resolving links
 
@@ -354,7 +354,7 @@ link_resolver = KenticoCloud::Delivery::Resolvers::ContentLinkResolver.new(lambd
   return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
 end)
 delivery_client = KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                               content_link_url_resolver: link_resolver
+                                                             content_link_url_resolver: link_resolver
 ```
 
 You can also build the logic for your resolver in a separate class and register an instance of that class in the DeliveryClient. The class must extend `KenticoCloud::Delivery::Resolvers::ContentLinkResolver` and contain a `resolve_link(link)` method. For example, you can create `MyLinkResolver.rb`:
@@ -372,7 +372,7 @@ Then create an object of this class when instantiating the DeliveryClient:
 
 ```ruby
 delivery_client = KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                               content_link_url_resolver: MyLinkResolver.new
+                                                             content_link_url_resolver: MyLinkResolver.new
 ```
 
 You can pass a `ContentLinkResolver` to the DeliveryQuery instead of the client if you only want to resolve links for that query, or they should be resolved differently:
@@ -399,7 +399,7 @@ item_resolver = KenticoCloud::Delivery::Resolvers::ContentLinkResolver.new(lambd
   return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
 end)
 delivery_client = KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                               content_link_url_resolver: item_resolver
+                                                             content_link_url_resolver: item_resolver
 delivery_client.item('coffee_processing_techniques').execute do |response|
   text = response.item.get_string 'body_copy'
 end
@@ -415,7 +415,7 @@ item_resolver = KenticoCloud::Delivery::Resolvers::InlineContentItemResolver.new
       return "<div>$#{item.elements.price.value}</div>" if item.system.type.eql? 'brewer'
     end)
 delivery_client = KenticoCloud::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                               inline_content_item_resolver: item_resolver
+                                                             inline_content_item_resolver: item_resolver
 ```
 
 The object passed to the resolving method is a complete ContentItem. Similar to content link resolvers, you can create your own class which extends `KenticoCloud::Delivery::Resolvers::InlineContentItemResolver` and implements the `resolve_item` method:
@@ -445,8 +445,8 @@ When you've obtained the URL for an asset, you can use our [Image Transformation
 ```ruby
 url = response.item.get_assets('teaser_image').first.url
 url = KenticoCloud::Delivery::Builders::ImageTransformationBuilder.transform(url)
-                                                    # methods...
-                                                    .url
+                                                                  # methods...
+                                                                  .url
 ```
 
 The available methods are:

data/lib/delivery/client/delivery_query.rb

@@ -141,6 +141,7 @@ module KenticoCloud
       #   - +self+
       def language(value)
         query_string.set_param('language', value)
+        self
       end
 
       # Sets the 'limit' query string parameter for paging results, or just to

data/lib/delivery/version.rb

@@ -1,5 +1,5 @@
 module KenticoCloud
   module Delivery
-    VERSION = '1.0.0'.freeze
+    VERSION = '1.0.1'.freeze
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: delivery-sdk-ruby
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Eric Dugre
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-03-21 00:00:00.000000000 Z
+date: 2019-03-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: nokogiri