active_mappers 1.4.0 → 1.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: aeca810a9999765703a5f64cc394c4b30cbb2d0891f6648c5402efa1d336ffdd
-  data.tar.gz: 8e77fda2149230f5bab01d50083bd8254b84bd34d28306abc86f829a7741d151
+  metadata.gz: c6645f47b539aaf463969e77a0124e6f175e1d416062a1b20b3cfb844a70d7f1
+  data.tar.gz: e9281f76b54f95f5435aefd6d546456ad2e8370f747603360cc6623727c42a85
 SHA512:
-  metadata.gz: 7cc3c0b2848d31fc0edf7448fcacf68cbce32c9919255363199d9fbfdc86ce97e8d779effb4187ddb3d93157042fc69e7037d5ebf418ebcc702830e6301906f0
-  data.tar.gz: 337e71b30d908254f7e394d7767888fcd90bcd7a70b1a88796a315d68de7bcda105986f3b0d5746b1d292a7a4a8af35a8eee17e730fc765ed84a533430ee4918
+  metadata.gz: 6d1b60f6a7a67fd6f258427c202955cc4a60fcf143d57b4ccd6b10aa1b9d88e95ffeb3874cd72dcf997a5836dd7a59914be75bf7358d426bbabfb97a9195b4df
+  data.tar.gz: 0a921774c1c38eee7d0ec1adbf436676190bbdb2b2b3e396da146aec2bc024acd278ee49cd469017e32d26db03ea17e0f0a28888afade69c297417b2954ba7e6

data/README.md

@@ -32,7 +32,7 @@ Then, depending on your usage you may want to create an `app/mappers` folder in
 
 You will put all your mappers inside of it.
 
-## Usage
+## Basic usage
 
 ```ruby
 UserMapper.with(user)
@@ -49,7 +49,7 @@ UserMapper.with(user)
 # }
 ```
 
-### Setup (optional)
+## Setup (optional)
 
 You may want to customize some parts of ActiveMappers behavior.
 
@@ -71,7 +71,7 @@ Here is the list of configurable options
 | `ignored_namespaces`    | `Array`   | `[]`      | Namespaces to ignore when generating json root key name            |
 | `root_keys_transformer` | `Proc`    | See below | Custom way to change a mapper class name into a JSON root key      |
 
-**Root Keys Transformer**
+### Root Keys Transformer
 
 A root key transform is used to transform the mapper class name into a JSON root key name.
 
@@ -101,9 +101,9 @@ config.root_keys_transformer = proc do |key|
 end
 ```
 
-### Creating a mapper
+## API
 
-**Declaring your attributes**
+### Declaring your attributes
 
 Most basic usage, just declare the attributes you want to display.
 
@@ -113,7 +113,7 @@ class UserMapper < ActiveMappers::Base # You must extend ActiveMappers::Base in
 end
 ```
 
-**Delegating your attributes**
+### Delegating your attributes
 
 Say you have a model with the following structure :
 
@@ -144,7 +144,7 @@ class UserMapper < ActiveMappers::Base
 end
 ```
 
-**Declaring relationship**
+### Declaring relationship
 
 You can declare any type of relationship (`has_one`, `belongs_to`, `has_many`, etc) and the mapper that matches it will automatically be fetched and used.
 
@@ -179,14 +179,13 @@ It also works with namespaced resources.
 
 If you need you can specify more options :
 
-````ruby
+```ruby
 class UserMapper < ActiveMappers::Base
   relation :account, AccountMapper, scope: :admin
 end
+```
 
-
-
-**Declaring polymorphic relationships**
+### Declaring polymorphic relationships
 
 Consider the following polymorphic relation :
 
@@ -202,7 +201,7 @@ end
 class NormalUser
   has_many :posts, class_name: 'Post', as: :author
 end
-````
+```
 
 In order to use the `author` polymorphic attribute in your `PostMapper` you need to declare the following :
 
@@ -226,7 +225,7 @@ end
 
 Then, based of the `XXX_type` column, the mapper will automatically resolve to either `AdminUserMapper` or `NormalUserMapper`
 
-**Rendering a collection of different classes**
+### Rendering a collection of different classes
 
 Say you want to render many resources with a single Mapper
 
@@ -266,7 +265,7 @@ Will generate the following :
 
 Again, just like the above polymorphic declaration, the mapper will automatically resolve to the corresponding one.
 
-**Custom Attributes**
+### Custom Attributes
 
 If you need to implement custom attributes you can always use the `each` statement.
 
@@ -299,7 +298,7 @@ Will generate the following:
 You can declare any number of `each` in a single mapper.
 Actually, `each` is used to implement every above features.
 
-**Context**
+### Context
 
 In most cases declaring your mapper with your resource should be enough. However, sometimes you may need to give your mapper a context in order to allow it to resolve a method or something else.
 
@@ -317,7 +316,7 @@ end
 RewardMapper.with(reward, context: user)
 ```
 
-**Scope**
+### Scope
 
 ActiveMappers does not yet support inheritance. However we provide an even better alternative named `scope`.
 
@@ -385,7 +384,7 @@ By default, root will be enabled, meaning a UserMapper, will generate a JSON pre
 }
 ```
 
-**Custom Root**
+### Custom Root
 
 If you want to customize the root name, you can use
 
@@ -401,7 +400,7 @@ which will generate :
 }
 ```
 
-**Rootless**
+### Rootless
 
 If you do not want to set any root, use :
 

data/active_mappers.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name        = 'active_mappers'
-  s.version     = '1.4.0'
+  s.version     = '1.4.1'
   s.date        = '2019-05-10'
   s.summary     = 'Slick, fast view layer for you Rails API.'
   s.description = 'Fast, simple, declarative way to design your API\'s view layer'

data/lib/active_mappers.rb

@@ -56,8 +56,12 @@ module ActiveMappers
 
     def self.polymorphic(key)
       each do |resource|
-        resource_mapper = "#{KeyTransformer.base_namespace(self)}::#{resource.send("#{key}_type")}Mapper".constantize
-        { key => resource_mapper.with(resource.send(key), rootless: true) }
+        if polymorphic_resource = resource.send("#{key}_type")
+          resource_mapper = "#{KeyTransformer.base_namespace(self)}::#{polymorphic_resource}Mapper".constantize
+          { key => resource_mapper.with(resource.send(key), rootless: true) }
+        else
+          {}
+        end
       end
     end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: active_mappers
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 1.4.1
 platform: ruby
 authors:
 - Michaël Villeneuve
@@ -116,8 +116,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.7.3
+rubygems_version: 3.0.1
 signing_key: 
 specification_version: 4
 summary: Slick, fast view layer for you Rails API.