entangled 0.0.17 → 0.0.18

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 620c93edc4a4892c41fe62cfd60cd448a245621e
-  data.tar.gz: d0cde74b9d171662e6bb716349a80eedcf943441
+  metadata.gz: c26b49537871a591ca346338518c72959721f39a
+  data.tar.gz: b1edc3cd5f06358c30ce85ef8146da53db890704
 SHA512:
-  metadata.gz: 24ee4a89da4c1ff4dd462ea2b34f335cb9c05aea74488a6682e6ab6959e0388b3894262ff4adde9f15896c039f8de9a9015d0cce61e794e7a91fa322771493d0
-  data.tar.gz: 34d56b6e058a103daa410ca346e01165ff5de40eccab0c04c61c8ee5ec13029498f991106dc8b97d012fa1712123a3d93376bf0b73ba949703818143edb86747
+  metadata.gz: 54880c5779d9979ac8f97728b5e939fa3af5ffff4e76a5f330314cf3eb9b1fd7d609cd15e2be8ba6273019c5441db8d59788013763f2c4c15758024bb70c4e31
+  data.tar.gz: 98ab954df3d7f04be3bd6a8f0662a33f0b88626e5ab06c6b5351d3721a3c7de63350af215da5ead09d6e29c2c61434b2aefe1ff9bc5eb11d2f12de68281da86d

data/README.md

@@ -2,11 +2,11 @@
 
 [![Codeship Status for dchacke/entangled](https://codeship.com/projects/9fe9a790-9df7-0132-5fb8-6e77ea26735b/status?branch=master)](https://codeship.com/projects/64679)
 
-Services like Firebase are great because they provide real time data binding between client and server. But they come at a price: You give up control over your back end. Wouldn't it be great to have real time functionality but still keep your beloved Rails back end? That's where Entangled comes in.
+Real time is important. Users have come to expect real time behavior from every website, because they want to see the latest data without having to reload the page. Real time increases their engagement, provides better context for the data they're seeing, and makes collaboration easier.
 
-Entangled stores and syncs data instantly across every device. It is a layer behind your controllers and models that pushes updates to all connected clients in real time. It is cross-browser compatible and even offers real time validations.
+Entangled stores and syncs data from ActiveRecord instantly across every device. It is a layer behind your models and controllers that pushes updates to all connected clients in real time. It is cross-browser compatible and offers real time validations.
 
-Real time data binding should be the default, not an add-on. Entangled aims at making real time features as easy to implement as possible, while at the same time making your restful controllers thinner. All this without having to give up control over your back end.
+Currently, Entangled runs on Rails 4.2 in the back end and Angular in the front end.
 
 ## Installation
 Add this line to your application's Gemfile:
@@ -130,7 +130,7 @@ end
 
 Note the following:
 
-- All methods are wrapped in a new `broadcast` block needed to send messages to connected clients
+- All methods are wrapped in a new `broadcast` block needed to receive and send data to connected clients
 - The `index` method will expect an instance variable with the same name as your controller in the plural form (e.g. `@messages` in a `MessagesController`)
 - The `show`, `create` and `update` methods will expect an instance variable with the singular name of your controller (e.g. `@message` in a `MessagesController`)
 - Data sent to clients arrives as stringified JSON
@@ -152,7 +152,7 @@ If you store your Redis instance in `$redis` or `REDIS` (e.g. in an initializer)
 Depending on your app's settings, you might have to increase the pool size in your database.yml configuration file, since every new socket will open a new connection to your database.
 
 ## The Client
-You will need to configure your client to create Websockets and understand incoming requests on those sockets. If you use Angular for your front end, you can use the Angular library from this repository. The use of Angular as counterpart of this gem is highly recommended, since its inherent two way data binding complements the real time functionality of this gem nicely.
+You will need to configure your client to create Websockets and understand incoming requests on those sockets. In order to use the helper methods for the front end provided by the Entangled Angular library, you must use Angular in your front end. The use of Angular as counterpart of this gem is highly recommended, since its inherent two way data binding complements the real time functionality of this gem nicely.
 
 ### Installation
 You can either download or reference the file `entangled.js` from this repository, or simply install it with Bower:
@@ -180,7 +180,7 @@ app.factory('Message', function(Entangled) {
 
 In the above example, first we inject Entangled into our service, then instantiate a new Entangled object and return it. The Entangled object takes one argument when instantiated: the URL of your resource's index action (in this case, `/messages`). Note that the socket URL looks just like a standard restful URL with http, except that the protocol part has been switched with `ws` to use the websocket protocol. Also note that you need to use `wss` instead if you want to use SSL.
 
-The Entangled service come with these functions:
+The Entangled service comes with these functions:
 
 - `new(params)`
 - `create(params, callback)`
@@ -245,12 +245,7 @@ $scope.message.$destroy(function() {
 });
 ```
 
-All functions above will interact with your server's controllers in real time.
-
-If data in your server's database changes, so will your scope variables - in real time, for all connected clients.
-
-### Available Functions
-A number of functions is attached to Entangled JavaScript objects. They basically mimic ActiveRecord's behavior in the back end to make the database more accessible in the front end.
+All functions above will interact with your server's controllers in real time. Your scope variables will always reflect your server's most current data.
 
 #### Validations
 Objects from the Entangled service automatically receive ActiveRecord's error messages from your model when you `$save()`. An additional property called `errors` containing the error messages is available, formatted the same way you're used to from calling `.errors` on a model in Rails.
@@ -291,7 +286,7 @@ $scope.message.$save(function() {
 Note that `$valid()` and `$invalid()` should only be used after $saving a resource, i.e. in the callback of `$save`, since they don't actually invoke server side validations. They only check if a resource contains errors.
 
 #### Persistence
-Just like with ActiveRecord's `persisted?` method, you can use `$persisted()` on an object to check if it was successfully stored in the database.
+Just as with ActiveRecord's `persisted?` method, you can use `$persisted()` on an object to check if it was successfully stored in the database.
 
 ```javascript
 $scope.message.$persisted();
@@ -302,16 +297,28 @@ $scope.message.$persisted();
 This gem is best used for Rails apps that serve as APIs only and are not concerned with rendering views, since Entangled controllers cannot render views. A front end separate from your Rails app is recommended, either in your Rails app's public directory, or a separate front end app altogether.
 
 ## Limitations
-The gem rely's heavily on convention over configuration and currently only works with restful style controllers as shown above. More customization will be available soon.
+The gem relies heavily on convention over configuration and currently only works with restful style controllers as shown above. More features will be available soon, such as associations, authentication, and more.
+
+## Development Priorities
+The following features are to be implemented next:
+
+- Offline capabilities - when client is disconnected, put websocket interactions in a queue and dequeue all once connected again
+- Support for authentication
+- Remove angular dependencies from bower package (they're currently all being downloaded as well when doing bower install)
+- On Heroku (maybe in production in general), objects are always in different order depending on their attributes
+- Add $onChange listener to objects
+- Add diagram on how it works to Readme
+- Reuse open DB connections to reduce pool-size - currently, a new db connection is established for every request, which quickly gets out of hand. Only one DB connection should be opened and maintained per client
+- Check if Rails 4.0.0 supported too
 
 ## Contributing
 1. [Fork it](https://github.com/dchacke/entangled/fork) - you will notice that the repo comes with a back end and a front end part to test both parts of the gem
 2. Run `$ bundle install` in the root of the repo
 3. Run `$ bower install` and `$ npm install` in spec/dummy/public
-4. The back end example app resides in spec/dummy; you can run `rails` and `rake` commands in there if you prefix them with `bin/`, i.e. `$ bin/rails s` or `$ bin/rake db:schema:load`; run your tests in the root of the repo by running `$ rspec`
-5. The front end example app resides in spec/dummy/public. To look at it in your browser, cd into spec/dummy/public and run `$ bin/rails s`. Tests for this part of the app can be located under spec/dummy/public/test and are written with Jasmine. To run the tests, first run `$ bin/rails -e test` to start up the server in test mode, and then run `$ grunt test` in a new terminal tab. It's important to remember that changes you make to the server will not take effect until you restart the server since you're running it in the test environment! Also remember to prepare the test database by running `$ bin/rake db:test:prepare`
-6. The Entangled Angular service resides in spec/dummy/public/app/entangled/entangled.js. This is where you can make changes to the service; a copy of it, living in /entangled.js at the root of the repo, should be kept in sync for it to be available with Bower, so it's best if you replace this file with the one from the dummy app should have made any changes to the latter
-7. Write your tests
+4. The back end example app resides in spec/dummy. You can run `rails` and `rake` commands in there if you prefix them with `bin/`, i.e. `$ bin/rails s` or `$ bin/rake db:schema:load`. Run your Rails tests in the root of the repo by running `$ rspec`
+5. The front end example app resides in spec/dummy/public. To look at it in your browser, cd into spec/dummy/public and run `$ bin/rails s`. Tests for this part of the app can be located under spec/dummy/public/test and are written with Jasmine. To run the tests, first run `$ bin/rails -e test` to start up the server in test mode, and then run `$ grunt test` in a new terminal tab. It's important to remember that changes you make to the server will not take effect until you restart the server since you're running it in the test environment. Also remember to prepare the test database by running `$ bin/rake db:test:prepare`
+6. The Entangled Angular service resides in spec/dummy/public/app/entangled/entangled.js. This is where you can make changes to the service. A copy of it, living in /entangled.js at the root of the repo, should be kept in sync for it to be available with Bower. Once you're done editing spec/dummy/public/app/entangled/entangled.js, copy it over to /entangled.js
+7. Write your tests. Test coverage is required
 8. Write your feature to make the tests pass
 9. Stage and commit your changes
 10. Push to a new feature branch in your repo

data/bower.json

@@ -11,7 +11,6 @@
     "lib",
     "spec",
     ".gitignore",
-    "entangled-0.0.9.gem",
     "entangled.gemspec",
     "Gemfile",
     "Gemfile.lock",

data/entangled.js

@@ -1,269 +1 @@
-// Register Angular module and call it 'entangled'
-angular.module('entangled', [])
-
-// Register service and call it 'Entangled'
-.factory('Entangled', function() {
-  // Every response coming from the server will be wrapped
-  // in a Resource constructor to represent a CRUD-able
-  // resource that can be saved and destroyed using the
-  // methods $save() and $destroy. A Resource also
-  // stores the socket's URL it was retrieved from so it
-  // can be reused for other requests.
-  var Resource = function(params, webSocketUrl) {
-    // Assign proerties
-    for (var key in params) {
-      // Skip inherent object properties
-      if (params.hasOwnProperty(key)) {
-        this[key] = params[key];
-      }
-    }
-
-    this.webSocketUrl = webSocketUrl;
-  };
-
-  // $save() will send a request to the server
-  // to either create a new record or update
-  // an existing, depending on whether or not
-  // an id is present.
-  Resource.prototype.$save = function(callback) {
-    var that = this;
-
-    if (this.id) {
-      // Update
-      var socket = new WebSocket(that.webSocketUrl + '/' + that.id + '/update');
-      socket.onopen = function() {
-        socket.send(JSON.stringify(that));
-      };
-
-      // Receive updated resource from server
-      socket.onmessage = function(event) {
-        if (event.data) {
-          var data = JSON.parse(event.data);
-
-          // Assign/override new data (such as updated_at, etc)
-          if (data.resource) {
-            for (key in data.resource) {
-              that[key] = data.resource[key];
-            }
-          }
-        }
-
-        // Pass 'that' to callback for create
-        // function so that the create function
-        // can pass the created resource to its
-        // own callback; not needed for $save per se
-        if (callback) callback(that);
-      };
-    } else {
-      // Create
-      var socket = new WebSocket(that.webSocketUrl + '/create');
-
-      // Send attributes to server
-      socket.onopen = function() {
-        socket.send(JSON.stringify(that));
-      };
-
-      // Receive saved resource from server
-      socket.onmessage = function(event) {
-        if (event.data) {
-          var data = JSON.parse(event.data);
-
-          // Assign/override new data (such as id, created_at,
-          // updated_at, etc)
-          if (data.resource) {
-            for (key in data.resource) {
-              that[key] = data.resource[key];
-            }
-          }
-        }
-
-        // Pass 'that' to callback for create
-        // function so that the create function
-        // can pass the created resource to its
-        // own callback; not needed for $save per se
-        if (callback) callback(that);
-      };
-    }
-  };
-
-  // $update() updates a record in place
-  Resource.prototype.$update = function(params, callback) {
-    // Update object in memory
-    for (var key in params) {
-      // Skip inherent object properties
-      if (params.hasOwnProperty(key)) {
-        this[key] = params[key];
-      }
-    }
-
-    // Save object
-    this.$save(callback);
-  };
-
-  // $destroy() will send a request to the server to
-  // destroy an existing record.
-  Resource.prototype.$destroy = function(callback) {
-    var socket = new WebSocket(this.webSocketUrl + '/' + this.id + '/destroy');
-    socket.onopen = function() {
-      // It's fine to send an empty message since the
-      // socket's URL contains all the information
-      // needed to destroy the record (the id).
-      socket.send(null);
-
-      if (callback) callback();
-    };
-  };
-
-  // $valid() checks if any errors are attached to the object
-  // and return false if so, false otherwise. This doesn't actually
-  // invoke server side validations, so it should only be used
-  // after calling $save() to check if the record was successfully
-  // stored in the database
-  Resource.prototype.$valid = function() {
-    return !(this.errors && Object.keys(this.errors).length);
-  };
-
-  // $invalid() returns the opposite of $valid()
-  Resource.prototype.$invalid = function() {
-    return !this.$valid();
-  };
-
-  // $persisted() checks if the record was successfully stored
-  // in the back end's database
-  Resource.prototype.$persisted = function() {
-    return !!this.id;
-  };
-
-  // Resources wraps all individual Resource objects
-  // in a collection.
-  var Resources = function(resources, webSocketUrl) {
-    this.all = [];
-
-    for (var i = 0; i < resources.length; i++) {
-      var resource = new Resource(resources[i], webSocketUrl);
-      this.all.push(resource);
-    }
-  };
-
-  // Entangled is the heart of this service. It contains
-  // several methods to instantiate a new Resource,
-  // retrieve an existing Resource from the server,
-  // and retrieve a collection of existing Resources
-  // from the server.
-  // 
-  // Entangled is a constructor that takes the URL
-  // of the index action on the server where the
-  // Resources can be retrieved.
-  var Entangled = function(webSocketUrl) {
-    // Store the root URL that sockets
-    // will connect to
-    this.webSocketUrl = webSocketUrl;
-  };
-
-  // Function to instantiate a new Resource, optionally
-  // with given parameters
-  Entangled.prototype.new = function(params) {
-    return new Resource(params, this.webSocketUrl);
-  };
-
-  // Retrieve all Resources from the root of the socket's
-  // URL
-  Entangled.prototype.all = function(callback) {
-    var socket = new WebSocket(this.webSocketUrl);
-
-    socket.onmessage = function(event) {
-      // If the message from the server isn't empty
-      if (event.data.length) {
-        // Convert message to JSON
-        var data = JSON.parse(event.data);
-
-        // If the collection of Resources was sent
-        if (data.resources) {
-          // Store retrieved Resources in property
-          this.resources = new Resources(data.resources, socket.url);
-        } else if (data.action) {
-          if (data.action === 'create') {
-            // If new Resource was created, add it to the
-            // collection
-            this.resources.all.push(new Resource(data.resource, socket.url));
-          } else if (data.action === 'update') {
-            // If an existing Resource was updated,
-            // update it in the collection as well
-            var index;
-
-            for (var i = 0; i < this.resources.all.length; i++) {
-              if (this.resources.all[i].id === data.resource.id) {
-                index = i;
-              }
-            }
-
-            this.resources.all[index] = new Resource(data.resource, socket.url);
-          } else if (data.action === 'destroy') {
-            // If a Resource was destroyed, remove it
-            // from Resources as well
-            var index;
-
-            for (var i = 0; i < this.resources.all.length; i++) {
-              if (this.resources.all[i].id === data.resource.id) {
-                index = i;
-              }
-            }
-
-            this.resources.all.splice(index, 1);
-          } else {
-            console.log('Something else other than CRUD happened...');
-            console.log(data);
-          }
-        }
-      }
-
-      // Run the callback and pass in the
-      // resulting collection
-      callback(this.resources.all);
-    };
-  };
-
-  // Instantiate and persist a record in one go
-  Entangled.prototype.create = function(params, callback) {
-    var resource = this.new(params);
-    resource.$save(callback);
-  };
-
-  // Find an individual Resource on the server
-  Entangled.prototype.find = function(id, callback) {
-    var webSocketUrl = this.webSocketUrl;
-    var socket = new WebSocket(webSocketUrl + '/' + id);
-
-    socket.onmessage = function(event) {
-      // If the message from the server isn't empty
-      if (event.data.length) {
-        // Parse message and convert to JSON
-        var data = JSON.parse(event.data);
-
-        if (data.resource && !data.action) {
-          // If the Resource was sent from the server,
-          // store it
-          this.resource = new Resource(data.resource, webSocketUrl);
-        } else if (data.action) {
-          if (data.action === 'update') {
-            // If the stored Resource was updated,
-            // update it here as well
-            this.resource = new Resource(data.resource, webSocketUrl);
-          } else if (data.action === 'destroy') {
-            // If the stored Resource was destroyed,
-            // remove it from here as well
-            this.resource = undefined;
-          }
-        } else {
-          console.log('Something else other than CRUD happened...');
-          console.log(data);
-        }
-      }
-
-      // Run callback with retrieved Resource
-      callback(this.resource);
-    };
-  };
-
-  return Entangled;
-});
+angular.module("entangled",[]).factory("Entangled",function(){var e=function(e,r){for(var t in e)e.hasOwnProperty(t)&&(this[t]=e[t]);this.webSocketUrl=r};e.prototype.$save=function(e){var r=this;if(this.id){var t=new WebSocket(r.webSocketUrl+"/"+r.id+"/update");t.onopen=function(){t.send(JSON.stringify(r))},t.onmessage=function(t){if(t.data){var o=JSON.parse(t.data);if(o.resource)for(key in o.resource)r[key]=o.resource[key]}e&&e(r)}}else{var t=new WebSocket(r.webSocketUrl+"/create");t.onopen=function(){t.send(JSON.stringify(r))},t.onmessage=function(t){if(t.data){var o=JSON.parse(t.data);if(o.resource)for(key in o.resource)r[key]=o.resource[key]}e&&e(r)}}},e.prototype.$update=function(e,r){for(var t in e)e.hasOwnProperty(t)&&(this[t]=e[t]);this.$save(r)},e.prototype.$destroy=function(e){var r=new WebSocket(this.webSocketUrl+"/"+this.id+"/destroy");r.onopen=function(){r.send(null),e&&e()}},e.prototype.$valid=function(){return!(this.errors&&Object.keys(this.errors).length)},e.prototype.$invalid=function(){return!this.$valid()},e.prototype.$persisted=function(){return!!this.id};var r=function(r,t){this.all=[];for(var o=0;o<r.length;o++){var s=new e(r[o],t);this.all.push(s)}},t=function(e){this.webSocketUrl=e};return t.prototype["new"]=function(r){return new e(r,this.webSocketUrl)},t.prototype.all=function(t){var o=new WebSocket(this.webSocketUrl);o.onmessage=function(s){if(s.data.length){var n=JSON.parse(s.data);if(n.resources)this.resources=new r(n.resources,o.url);else if(n.action)if("create"===n.action)this.resources.all.push(new e(n.resource,o.url));else if("update"===n.action){for(var i,a=0;a<this.resources.all.length;a++)this.resources.all[a].id===n.resource.id&&(i=a);this.resources.all[i]=new e(n.resource,o.url)}else if("destroy"===n.action){for(var i,a=0;a<this.resources.all.length;a++)this.resources.all[a].id===n.resource.id&&(i=a);this.resources.all.splice(i,1)}else console.log("Something else other than CRUD happened..."),console.log(n)}t(this.resources.all)}},t.prototype.create=function(e,r){var t=this["new"](e);t.$save(r)},t.prototype.find=function(r,t){var o=this.webSocketUrl,s=new WebSocket(o+"/"+r);s.onmessage=function(r){if(r.data.length){var s=JSON.parse(r.data);s.resource&&!s.action?this.resource=new e(s.resource,o):s.action?"update"===s.action?this.resource=new e(s.resource,o):"destroy"===s.action&&(this.resource=void 0):(console.log("Something else other than CRUD happened..."),console.log(s))}t(this.resource)}},t});

data/lib/entangled/controller.rb

@@ -30,13 +30,17 @@ module Entangled
       # Channel name for collection of resources, used in index
       # action
       def collection_channel
-        resources_name
+        model.channel
+      end
+
+      # The model for this controller. E.g. Taco for a TacosController
+      def model
+        controller_name.classify.constantize
       end
 
       # Channel name for single resource, used in show action
       def member_channel
-        instance = member
-        "#{resources_name}/#{instance.to_param}"
+        member.channel
       end
 
       def collection

data/lib/entangled/model.rb

@@ -57,7 +57,7 @@ module Entangled
 
       # The inferred channel name. For example, if the class name
       # is DeliciousTaco, the inferred channel name is "delicious_tacos"
-      def inferred_channel_name
+      def channel
         name.underscore.pluralize
       end
 
@@ -79,6 +79,15 @@ module Entangled
         attributes.merge(errors: errors).as_json
       end
 
+      # The inferred channel name for a single record
+      # containing the inferred channel name from the class
+      # and the record's id. For example, if it's a
+      # DeliciousTaco with the id 1, the inferred channel
+      # name for the single record is "delicious_tacos/1"
+      def channel
+        "#{self.class.channel}/#{self.to_param}"
+      end
+
       private
 
       # Publishes to client. Whoever is subscribed
@@ -86,25 +95,16 @@ module Entangled
       # gets the message
       def publish(action)
         redis.publish(
-          self.class.inferred_channel_name,
+          self.class.channel,
           json(action)
         )
 
         redis.publish(
-          inferred_channel_name_for_single_record,
+          channel,
           json(action)
         )
       end
 
-      # The inferred channel name for a single record
-      # containing the inferred channel name from the class
-      # and the record's id. For example, if it's a
-      # DeliciousTaco with the id 1, the inferred channel
-      # name for the single record is "delicious_tacos/1"
-      def inferred_channel_name_for_single_record
-        "#{self.class.inferred_channel_name}/#{to_param}"
-      end
-
       # JSON containing the type of action (:create, :update
       # or :destroy) and the record itself. This is eventually
       # broadcast to the client

data/lib/entangled/version.rb

@@ -1,3 +1,3 @@
 module Entangled
-  VERSION = "0.0.17"
+  VERSION = "0.0.18"
 end

data/spec/models/message_spec.rb

@@ -6,9 +6,17 @@ RSpec.describe Message, type: :model do
   end
 
   describe 'Methods' do
-    describe '.inferred_channel_name' do
+    describe '.channel' do
       it 'is the underscore, pluralized model name' do
-        expect(Message.inferred_channel_name).to eq 'messages'
+        expect(Message.channel).to eq 'messages'
+      end
+    end
+
+    describe '#channel' do
+      let(:message) { Message.create(body: 'foo') }
+
+      it "is the class's channel name plus the member as param" do
+        expect(message.channel).to eq "messages/#{message.to_param}"
       end
     end
 
@@ -27,7 +35,7 @@ RSpec.describe Message, type: :model do
           redis = stub_redis
 
           expect(redis).to have_received(:publish).with(
-            'messages', {
+            Message.channel, {
               action: :create,
               resource: message
             }.to_json
@@ -38,7 +46,7 @@ RSpec.describe Message, type: :model do
           redis = stub_redis
 
           expect(redis).to have_received(:publish).with(
-            "messages/#{message.to_param}", {
+            message.channel, {
               action: :create,
               resource: message
             }.to_json
@@ -55,7 +63,7 @@ RSpec.describe Message, type: :model do
           message.update(body: 'bar')
 
           expect(redis).to have_received(:publish).with(
-            'messages', {
+            Message.channel, {
               action: :update,
               resource: message
             }.to_json
@@ -68,7 +76,7 @@ RSpec.describe Message, type: :model do
           message.update(body: 'bar')
 
           expect(redis).to have_received(:publish).with(
-            "messages/#{message.to_param}", {
+            message.channel, {
               action: :update,
               resource: message
             }.to_json
@@ -85,7 +93,7 @@ RSpec.describe Message, type: :model do
           message.destroy
 
           expect(redis).to have_received(:publish).with(
-            'messages', {
+            Message.channel, {
               action: :destroy,
               resource: message
             }.to_json
@@ -98,7 +106,7 @@ RSpec.describe Message, type: :model do
           message.destroy
 
           expect(redis).to have_received(:publish).with(
-            "messages/#{message.to_param}", {
+            message.channel, {
               action: :destroy,
               resource: message
             }.to_json

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: entangled
 version: !ruby/object:Gem::Version
-  version: 0.0.17
+  version: 0.0.18
 platform: ruby
 authors:
 - Dennis Charles Hackethal
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-03-06 00:00:00.000000000 Z
+date: 2015-03-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler