simple_ams 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 21432f80bcadd512b56d7d24023014944e746d2b
-  data.tar.gz: 0d8dc9ac8b88a4b25483168fc2c88023831ec863
+  metadata.gz: 7466c8f4a93d634a5694e11369c829b5cd125e2f
+  data.tar.gz: 40ca860c3304907242ed9b357b1d0f2663faf977
 SHA512:
-  metadata.gz: b8efe4cea91158fb2cc4e2ed7f45b464cd78e61ea45a97dbf1e42f066c493dc07d468fbe3d2317ea40838bd71e8766c2556be2fd222ec3fdb0de8a090bac155b
-  data.tar.gz: c390be3c1c6b9a91b95916f761e7c4ccdd98ee9653ac9df969c4e42e915f78dcfa81311ddb0eb0f83e427054f5be7e05d53750c018255b8d86d72d763d5cfc9c
+  metadata.gz: 2ec2ba04017b4db14d5178dcc6f9ac11b1a50035a5971bd8a8b6b3c1dd1aebdae307d953078a7fd498fb32f2f689f5658adc5ce909ed41bc7c60519be9762efc
+  data.tar.gz: ddd1b7ebfc152dd071a19f5cb23f1ce154aee16c33536d8cb4ad997376a855743d208eceef23b18d5ce6a64d79d53e9a03f6e2d1e1bc53f62c3499aeea951796

data/README.md

@@ -58,15 +58,16 @@ class UserSerializer
   #links can also take other options, as specified by RFC 8288
   link :root, '/api/v1/', rel: :user
   #link values can be dynamic as well through lambdas
-  link :posts, ->(obj) { "/api/v1/users/#{obj.id}/posts/" }, rel: :user
+  #lambdas take arguments the object to be serialized and the instantiated serializer
+  link :posts, ->(obj, s) { "/api/v1/users/#{obj.id}/posts/" }, rel: :user
   #if you also need dynamic options, you can return an array from the lambda
-  link :followers, ->(obj) { ["/api/v1/users/#{obj.id}/followers/", rel: obj.type] }
+  link :followers, ->(obj, s) { ["/api/v1/users/#{obj.id}/followers/", rel: obj.type] }
 
   #same with metas: can be static, dynamic and accept arbitrary options
-  meta :environment, ->(obj) { Rails.env.to_s }
+  meta :environment, ->(obj, s) { Rails.env.to_s }
 
   #same with form: can be static, dynamic and accept arbitrary options
-  form :create, ->(obj) { User::CreateForm.for(obj) }
+  form :create, ->(obj, s) { User::CreateForm.for(obj) }
 
   #or if you need something quite generic (and probably adapter-related)
   #again it follows the same patterns as link
@@ -80,7 +81,7 @@ class UserSerializer
     #here we use only links and meta
     link :root, '/api/v1/', rel: :user
     type :users
-    meta :count, ->(collection) { collection.count }
+    meta :count, ->(collection, s) { collection.count }
   end
 
   #note that most probably the only thing that you will need here is the `type`,
@@ -143,7 +144,7 @@ In any case, we have the following options:
   #makes sense to use it when initializing the Renderer
   serializer: UserSerializer,
   #can also be a lambda, in case of polymorphic records, ideal for ArrayRenderer
-  serializer: ->(obj){ obj.employee? ? EmployeeSerializer : UserSerializer }
+  serializer: ->(obj, s){ obj.employee? ? EmployeeSerializer : UserSerializer }
   #specifying the underlying adapter. This cannot be a lambda in case of ArrayRenderer,
   #but can take some useful options that are passed down straight to the adapter class.
   adapter: SimpleAMS::Adapters::AMS, root: true
@@ -156,18 +157,18 @@ In any case, we have the following options:
     posts: "/api/v1/posts/", rel: :posts,
     #it can also be a lambda that takes the resource to be rendered as a param
     #when the lambda is called, it should return the array structure above
-    self: ->(obj) { ["/api/v1/users/#{obj.id}", rel: :user] }
+    self: ->(obj, s) { ["/api/v1/users/#{obj.id}", rel: :user] }
   },
   #the meta data, same as the links data (available in adapters even for single records)
   metas: {
-    type: ->(obj){ obj.employee? ? :employee : :user}
+    type: ->(obj, s){ obj.employee? ? :employee : :user}
     #meta can take arbitrary options as well
     authorization: :oauth, type: :bearer_token
   },
   #the form data, same as the links/metas data (available in adapters even for single records)
   forms: {
-    update: ->(obj){ User::UpdateForm.for(obj)}
-    follow: ->(obj){ User::FollowForm.for(obj)}
+    update: ->(obj, s){ User::UpdateForm.for(obj)}
+    follow: ->(obj, s){ User::FollowForm.for(obj)}
   },
   #collection parameters, used only in ArrayRenderer
   collection: {
@@ -175,10 +176,10 @@ In any case, we have the following options:
       root: '/api/v1'
     },
     metas: {
-      pages: ->(obj) { [obj.pages, collection: true]},
-      current_page: ->(obj) { [obj.current_page, collection: true] },
-      previous_page: ->(obj) { [obj.previous_page, collection: true] },
-      next_page: ->(obj) { [obj.next_page, collection: true] },
+      pages: ->(obj, s) { [obj.pages, collection: true]},
+      current_page: ->(obj, s) { [obj.current_page, collection: true] },
+      previous_page: ->(obj, s) { [obj.previous_page, collection: true] },
+      next_page: ->(obj, s) { [obj.next_page, collection: true] },
       max_per_page: 50,
     },
     #creating a resource goes in the collection route (users/), hence inside collection options ;)

data/lib/simple_ams/adapters/ams.rb

@@ -9,6 +9,8 @@ class SimpleAMS::Adapters::AMS
   end
 
   def as_json
+    return nil if document.resource.nil?
+
     hash = {}
 
     hash.merge!(fields)

data/lib/simple_ams/version.rb

@@ -1,3 +1,3 @@
 module SimpleAMS
-  VERSION = "0.1.2"
+  VERSION = "0.1.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: simple_ams
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Filippos Vasilakis
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-10-01 00:00:00.000000000 Z
+date: 2018-10-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler