hyper-mesh 0.6.0 → 1.0.0.lap22

data/Gemfile

@@ -1,10 +1,4 @@
 source 'https://rubygems.org'
-# Specify your gem's dependencies in synchromesh.gemspec
-# gem 'hyper-trace'
-# gem 'opal-browser'
-# gem 'hyper-operation', path: '../hyper-operation' #git: 'https://github.com/ruby-hyperloop/hyper-operation.git' #
-# gem 'hyper-component', path: '../hyper-component'
-# gem 'hyper-react', path: '../hyper-react'
-# gem 'hyper-store', path: '../hyper-store'
-# gem 'hyperloop-config', path: '../hyperloop-config'
+gem "opal-jquery", git: "https://github.com/opal/opal-jquery.git", branch: "master"
+gem "opal-rails", git: "https://github.com/opal/opal-rails.git", branch: "master"
 gemspec

data/README.md

@@ -1,283 +1,51 @@
-#  ![](https://github.com/Serzhenka/hyper-loop-logos/blob/master/hyper-mesh_150.png?raw=true)Hyper-model
+<div class="githubhyperloopheader">
 
-[![Join the chat at https://gitter.im/reactrb/chat](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/reactrb/chat?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
-[![Gem Version](https://badge.fury.io/rb/hyper-mesh.svg)](https://badge.fury.io/rb/hyper-mesh)
-
-TODO  There is no functional change. Config stuff goes in hyper-operation readme. AR interface stuff goes in hyper-model
-policies you have to think about... probably a seperate doc that both refer to, maybe with sections that say "Active Record only" or something like that."
-
-In Hyperloop, your ActiveRecord Models are available in your Isomorphic code.
-
-Components, Operations, and Stores have CRUD access to your server side ActiveRecord Models, using the standard ActiveRecord API.
-
-In addition, Hyperloop implements push notifications (via a number of possible technologies) so changes to records on the server are dynamically pushed to all authorized clients.
-
-*It's Isomorphic Ruby in action.*
-
-In other words, one browser creates, updates, or destroys a Model, and the changes are persisted in ActiveRecord models and then broadcast to all other authorized clients.
-
-## Overview
-
-+ The `hyper-model` gem provides ActiveRecord Models to Hyperloop's Isomorphic architecture.
-+ You access your Model data in your Components, Operations, and Stores just like you would on the server or in an ERB or HAML view file.
-+ If an optional push transport is connected Hyperloop broadcasts any changes made to your ActiveRecord models as they are persisted on the server or updated by one of the authorized clients.
-+ Some Models can be designated as *server-only* which means they are not available to the Isomorphic code.
-
-For example, consider a simple model called `Dictionary` which might be part of Wiktionary type app.
-
-```ruby
-class Dictionary < ActiveRecord::Base
-
-  # attributes
-  #   word: string   
-  #   definition: text
-  #   pronunciation: string
-
-  scope :defined, -> { 'definition IS NOT NULL AND pronunciation IS NOT NULL' }
-end
-```
-
-Here is a very simple Hyperloop Component that shows a random word from the dictionary:
-
-```ruby
-class WordOfTheDay < Hyperloop::Component
-
-  def pick_entry!  
-    # pick a random word and assign the selected record to entry
-    @entry = Dictionary.defined.all[rand(Dictionary.defined.count)]
-    force_update! # redraw our component when the word changes
-    # Notice that we use standard ActiveRecord constructs to select our
-    # random entry value
-  end
-
-  # pick an initial entry before we mount our component...
-  before_mount :pick_entry
-
-  # Again in our render block we use the standard ActiveRecord API, such
-  # as the 'defined' scope, and the 'word', 'pronunciation', and
-  # 'definition' attribute getters.  
-  render(DIV) do
-    DIV { "total definitions: #{Dictionary.defined.count}" }
-    DIV do
-      DIV { @entry.word }
-      DIV { @entry.pronunciation }
-      DIV { @entry.definition }
-      BUTTON { 'pick another' }.on(:click) { pick_entry! }
-    end
-  end
-```
-
-For complete examples with *push* updates, see any of the apps in the `examples` directory, or build your own in 5 minutes following one of the quickstart guides:
-
-TODO links below
-
-+ [Rails 5 with ActionCable](/docs/action_cable_quickstart.md)
-+ [Using Pusher.com](/docs/pusher_quickstart.md)
-+ [Using Pusher-Faker](/docs/pusher_faker_quickstart.md)
-+ [Using Simple Polling](/docs/simple_poller_quickstart.md)  
-
-## Basic Installation and Setup
-
-The easiest way to install is to use the `hyper-rails` gem.
-
-TODO check install uses `--hyper-model`
-
-1. Add `gem 'hyper-rails'` to your Rails `Gemfile` development section.
-2. Install the Gem: `bundle install`
-3. Run the generator: `bundle exec rails g hyperloop:install --hyper-model` (or use `--all` to install all hyperloop gems)
-4. Update the bundle: `bundle update`
-
-TODO check validity and ensure generator does this move
-
-You will find a `hyperloop/models` folder has been added to the Rails.  To access a model on the client, move it into the `hyperloop/models` folder.  If you are on Rails 5, you will also need to move the `application_record.rb` into this folder.
-
-You will also find an `app/policies` folder with a simple access policy suited for development.  Policies are how you will provide detailed access control to your Isomorphic models.  More details [here](/docs/authorization-policies.md).
-
-TODO fix link above
-
-To summarize:
-
-+ Your Isomorphic Models are moved to `hyperloop/models`. These are accessible to your Components, Operations, and Stores from either the server or the client.
-+ If you need to have server-only Models, they remain in `app/models`. These models are **not** accessible to your Isomorphic code.
-
-## Setting up the Push Transport
-
-To have changes to your Models on the server broadcast to authorized clients, add a Hyperloop initializer file and specify a transport.  For example to setup a simple polled transport add this file:
-
-TODO check below
-
-```ruby
-# config/initializers/hyperloop.rb
-Hyperloop.configuration do |config|
-  config.transport = :simple_poller
-end
-```
-
-After restarting, and reloading your browsers you will see changes broadcast to the clients.  You can also play with this by firing up a rails console, and creating, changing or destroying Models at the console.
-
-For setting up the other possible transports following one of these guides:
-
-TODO fix links below
-
-+ [Rails 5 with ActionCable](/docs/action_cable_quickstart.md)
-+ [Using Pusher.com](/docs/pusher_quickstart.md)
-+ [Using Pusher-Faker](/docs/pusher_faker_quickstart.md)
-+ [Using Simple Polling](/docs/simple_poller_quickstart.md)
-
-## Advanced Configuration
-
-TODO fix links below
-
-The above guides will work in most cases, but for complete details on configuration settings go [here](/docs/configuration_details.md)
+<p align="center">
 
-## ActiveRecord API
+<a href="http://ruby-hyperloop.org/" alt="Hyperloop" title="Hyperloop">
+<img width="350px" src="http://ruby-hyperloop.org/images/hyperloop-github-logo.png">
+</a>
 
-Hyperloop uses a large subset of the ActiveRecord API, modified only when necessary to accommodate the asynchronous nature of the client.  You can access your ActiveRecord models just like you would in Models, Controllers, or in ERB or HAML view templates.
+</p>
 
-TODO fix links below
+<h2 align="center">The Complete Isomorphic Ruby Framework</h2>
 
-See this [guide](/docs/activerecord_api.md) for details.
+<br>
 
-**Note** currently the `attributes` method is supported, but please do not use it as some details of the semantics will be changing in an upcoming release.  Instead of `foo.attributes[:xyz]` use `foo.send('xyz')` for now.
+<a href="http://ruby-hyperloop.org/" alt="Hyperloop" title="Hyperloop">
+<img src="http://ruby-hyperloop.org/images/githubhyperloopbadge.png">
+</a>
 
-## Client Side Scoping
+<a href="https://gitter.im/ruby-hyperloop/chat" alt="Gitter chat" title="Gitter chat">
+<img src="http://ruby-hyperloop.org/images/githubgitterbadge.png">
+</a>
 
-By default scopes will be recalculated on the server.  For simple scopes that do not use joins or includes no additional action needs to be taken to make scopes work with Hyperloop.  For scopes that do use joins, or if you want to offload the scoping computation from the server to the client read more [here.](docs/client_side_scoping.md)  
-
-TODO fix link above
-
-## Authorization
-
-Each application defines a number of *channels* and *authorization policies* for those channels and the data sent over the channels.
-
-Policies are defined with *Policy* classes.  These are similar and compatible with [Pundit](https://github.com/elabs/pundit) but
-you do not need to use the pundit gem (but can if you want.)
-
-TODO fix links below
-
-For complete details see [Authorization Policies](docs/authorization-policies.md)
-
-## Common Errors
-
-- **No policy class**
-  If you don't define a policy file, nothing will happen because nothing will get connected. By default Hyperloop will look for a `ApplicationPolicy` class.
-
-- **Wrong version of pusher-fake**  (pusher-fake/base vs. pusher-fake/rspec) See the Pusher-Fake gem repo for details.
-
-- Forgetting to add `require pusher` in application.js file  
-this results in an error like this:   
-  ```text
-  Exception raised while rendering #<TopLevelRailsComponent:0x53e>
-      ReferenceError: Pusher is not defined
-  ```  
-  To resolve make sure you `require 'pusher'` in your application.js file if using pusher.  DO NOT require pusher from your components manifest as this will cause prerendering to fail.
-
-- **No create/update/destroy policies**
-  You must explicitly allow changes to the Models to be made by the client. If you don't you will see 500 responses from the server when you try to update. To open all access do this in your application policy: `allow_change(to: :all, on: [:create, :update, :destroy]) { true }`
-
-- **Cannot connect to real pusher account**
-  If you are trying to use a real pusher account (not pusher-fake) but see errors like this  
-  ```text   
-  pusher.self.js?body=1:62 WebSocket connection to
-  'wss://127.0.0.1/app/PUSHER_API_KEY?protocol=7&client=js&version=3.0.0&flash=false'
-  failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
-  ```   
-  Check to see if you are including the pusher-fake gem.  
-  Hyperloop will always try to use pusher-fake if it sees the gem included.  Remove it and you should be good to go.  See [issue #5](https://github.com/hyper-react/HyperMesh/issues/5) for more details.
-
-- **Cannot connect with ActionCable.**  
-  Make sure that `config.action_cable.allowed_request_origins` includes the url you use for development (including the port) and that you are using `Puma`.
-
-- **Attributes are not being converted from strings, or do not have their default values**
-Eager loading is probably turned off.  Hyperloop needs to eager load `hyperloop/models` so it can find all the column information for all Isomorphic models.
-
-- **When starting rails you get a message on the rails console `couldn't find file 'browser'`**
-The `hyper-component` v0.10.0 gem removed the dependency on opal-browser.  You will have to add the 'opal-browser' gem to your Gemfile.
-
-- **On page load you get a message about super class mismatch for `DummyValue`**
-You are still have the old `reactive-record` gem in your Gemfile, remove it from your gemfile and your components manifest.
-
-- **On page load you get a message about no method `session` for `nil`**  
-You are still referencing the old reactive-ruby or reactrb gems either directly or indirectly though a gem like reactrb-router.  Replace any gems like `reactrb-router` with `hyper-router`.  You can also just remove `reactrb`, as `hyper-model` will be included by the `hyper-model` gem.
-
-- **You keep seeing the message `WebSocket connection to 'ws://localhost:3000/cable' failed: WebSocket is closed before the connection is established.`** every few seconds in the console.  
-  There are probably lots of reasons for this, but it means ActionCable can't get itself going.  One reason is that you are trying to run with Passenger instead of Puma, and trying to use `async` mode in cable.yml file.  `async` mode requires Puma.
-
-## Debugging
-
-Sometimes you need to figure out what connections are available, or what attributes are readable etc.
-
-Its usually all to do with your policies, but perhaps you just need a little investigation.
-
-TODO check rr has become hyperloop (as below)
-
-You can bring up a console within the controller context by browsing `localhost:3000/hyperloop/console`
-
-**Note:  change `rr` to wherever you are mounting Hyperloop in your routes file.**
-
-**Note: in rails 4, you will need to add the gem 'web-console' to your development section**
-
-Within the context you have access to `session.id` and current `acting_user` which you will need, plus some helper methods to reduce typing
-
-- Getting auto connection channels:  
-`channels(session_id = session.id, user = acting_user)`  
-e.g. `channels` returns all channels connecting to this session and user providing nil as the acting_user will test if connections can be made without there being a logged in user.
-
-- Can a specific class connection be made:
-`can_connect?(channel, user = acting_user)`
-e.g. `can_connect? Todo`  returns true if current acting_user can connect to the Todo class. You can also provide the class name as a string.
-
-- Can a specific instance connection be made:
-`can_connect?(channel, user = acting_user)`
-e.g. `can_connect? Todo.first`  returns true if current acting_user can connect to the first Todo Model. You can also provide the instance in the form 'Todo-123'
-
-- What attributes are accessible for a Model instance:  
-`viewable_attributes(instance, user = acting_user)`
-
-- Can the attribute be viewed:  
-`view_permitted?(instance, attribute, user = acting_user)`
-
-- Can a Model be created/updated/destroyed:
-`create_permitted?(instance, user = acting_user)`  
-e.g. `create_permitted?(Todo.new, nil)` can anybody save a new todo?  
-e.g. `destroy_permitted?(Todo.last)` can the acting_user destroy the last Todo
-
-You can of course simulate server side changes to your Models through this console like any other console.  For example
-
-`Todo.new.save` will broadcast the changes to the Todo Model to any authorized channels.
-
-## Development
-
-`hyper-model` is the merger of `reactive-record`, `synchromesh` and `hyper-mesh` gems.  As such a lot of the internal names are still using either ReactiveRecord or Synchromesh module names.
-
-The original `ReactiveRecord` specs were written in opal-rspec.  These are being migrated to use server rspec with isomorphic helpers.  There are about 150 of the original tests left and to run these you
-
-1. cd to `reactive_record_test_app`
-2. do a bundle install/update as needed,
-3. `bundle exec rake db:reset`,
-4. start the server: `bundle exec rails s`,
-5. then visit `localhost:3000/spec-opal`.
-
-If you want to help **PLEASE** consider spending an hour and migrate a spec file to the new format.  You can find examples by looking in the `spec/reactive_record/` directory and matching to the original file in
+[![Build Status](https://travis-ci.org/ruby-hyperloop/hyper-mesh.svg?branch=master)](https://travis-ci.org/ruby-hyperloop/hyper-mesh)
+[![Codeship Status for ruby-hyperloop/hyper-store](https://app.codeship.com/projects/4454c560-d4ea-0134-7c96-362b4886dd22/status?branch=master)](https://app.codeship.com/projects/202301)
+[![Gem Version](https://badge.fury.io/rb/hyper-mesh.svg)](https://badge.fury.io/rb/hyper-mesh)
 
-`reactive_record_test_app/spec_dont_run/moved_to_main_spec_dir`
+<p align="center">
+<img src="http://ruby-hyperloop.org/images/HyperModels.png" width="100" alt="Hyper-models">
+</p>
 
-The remaining tests are run in the more traditional `bundle exec rake`
+</div>
 
-or
+## Hyper-Mesh GEM is part of Hyperloop GEMS family
 
-```
-bundle exec rspec spec
-```
+Hyper-Mesh GEM comes with the Hyperloop GEM. 
 
-You can run the specs in firefox by adding `DRIVER=ff` (best for debugging.)  You can add `SHOW_LOGS=true` if running in poltergeist (the default) to see what is going on, but ff is a lot better for debug.
+But if you want to install it separately, please install the [Hyper-model GEM](https://github.com/ruby-hyperloop/hyper-model).
 
-## Contributing
+## Community
 
-TODO fix links
+#### Getting Help
+Please **do not post** usage questions to GitHub Issues. For these types of questions use our [Gitter chatroom](https://gitter.im/ruby-hyperloop/chat) or [StackOverflow](http://stackoverflow.com/questions/tagged/hyperloop).
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/reactive-ruby/HyperMesh. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](contributor-covenant.org) code of conduct.
+#### Submitting Bugs and Enhancements
+[GitHub Issues](https://github.com/ruby-hyperloop/hyperloop/issues) is for suggesting enhancements and reporting bugs. Before submiting a bug make sure you do the following:
+* Check out our [contributing guide](https://github.com/ruby-hyperloop/hyperloop/blob/master/CONTRIBUTING.md) for info on our release cycle.
 
 ## License
 
-The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+Hyperloop is released under the [MIT License](http://www.opensource.org/licenses/MIT).
+

data/Rakefile

@@ -3,9 +3,11 @@ require "rspec/core/rake_task"
 
 RSpec::Core::RakeTask.new(:spec)
 
-task :default do
-  sh 'DRIVER=pg bundle exec rspec spec/batch1 -f d'
-  sh 'DRIVER=pg bundle exec rspec spec/batch2 -f d'
-  sh 'DRIVER=pg bundle exec rspec spec/batch3 -f d'
-  sh 'DRIVER=pg bundle exec rspec spec/batch4 -f d'
+namespace :spec do
+  task :prepare do
+    sh %{bundle update}
+    sh %{cd spec/test_app; bundle update; bundle exec rails db:setup} # may need ;bundle exec rails db:setup as well
+  end
 end
+
+task :default => :spec

data/dciy.toml

@@ -0,0 +1,3 @@
+[dciy.commands]
+prepare = ["rake spec:prepare"]
+cibuild = ["bundle exec rake"]

data/hyper-mesh.gemspec

@@ -1,88 +1,66 @@
 # -*- encoding: utf-8 -*-
 $:.push File.expand_path('../lib/', __FILE__)
-
 require 'hypermesh/version'
 
-Gem::Specification.new do |s|
-
-    s.name          = "hyper-mesh"
-    s.version       = Hypermesh::VERSION
-    s.authors       = ["Mitch VanDuyn"]
-    s.email         = ["mitch@catprint.com"]
-
-    s.summary       = "React based CRUD access and Synchronization of active record models across multiple clients"
-    s.description   = "HyperMesh gives your HyperReact components CRUD access to your "\
-                      "ActiveRecord models on the client, using the the standard ActiveRecord "\
-                      "API. HyperMesh also implements push notifications (via a number of "\
-                      "possible technologies) so changes to records on the server are "\
-                      "dynamically updated on all authorised clients."
-    s.homepage      = "https://github.com/reactive-ruby/hyper-mesh"
-    s.license       = "MIT"
-
-    s.files          = `git ls-files`.split("\n")
-    s.executables    = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
-    s.test_files     = `git ls-files -- {test,spec,features}/*`.split("\n")
-    s.require_paths  = ['lib']
-
-    s.add_dependency 'activerecord', '>= 0.3.0'
-    s.add_dependency 'hyper-operation', '>= 0.5.0'
-    s.add_dependency 'hyper-component', '>= 0.12.3'
-
-    s.add_development_dependency 'bundler', '~> 1.8'
-    s.add_development_dependency 'rake', '~> 10.0'
-    s.add_development_dependency 'rspec-rails'
-    s.add_development_dependency 'timecop'
-
-    # For Test Rails App
-    s.add_development_dependency 'rails', '~>5.0.0' #'4.2.4'
-    s.add_development_dependency 'react-rails'
-    s.add_development_dependency 'opal-rails'
-    s.add_development_dependency 'opal-activesupport'
-    s.add_development_dependency 'factory_girl_rails'
-    s.add_development_dependency 'reactrb-rails-generator'
-    s.add_development_dependency 'rspec-wait'
-    s.add_development_dependency 'puma', '~> 3.6.0'
-
-    s.add_development_dependency 'pusher'
-    s.add_development_dependency 'pusher-fake'
-    s.add_development_dependency 'opal-browser'
-
-    # Keep linter-rubocop happy
-    s.add_development_dependency 'rubocop'
-
-    if RUBY_PLATFORM == 'java'
-      s.add_development_dependency 'jdbc-sqlite3'
-      s.add_development_dependency 'activerecord-jdbcsqlite3-adapter'
-      s.add_development_dependency 'therubyrhino'
-    else
-      s.add_development_dependency 'sqlite3', '1.3.10'
-      s.add_development_dependency 'mysql2' # for codeship
-      s.add_development_dependency 'therubyracer', '0.12.2'
+Gem::Specification.new do |spec|
+  spec.name          = 'hyper-mesh'
+  spec.version       = Hypermesh::VERSION
+  spec.authors       = ['Mitch VanDuyn', 'Jan Biedermann']
+  spec.email         = ['mitch@catprint.com', 'jan@kursator.com']
+  spec.summary       = 'React based CRUD access and Synchronization of active record models across multiple clients'
+  spec.description   = 'HyperMesh is the base for HyperModel. HyperModel gives your HyperComponents CRUD access to your '\
+                       'ActiveRecord models on the client, using the the standard ActiveRecord '\
+                       'API. HyperModel also implements push notifications (via a number of '\
+                       'possible technologies) so changes to records on the server are '\
+                       'dynamically updated on all authorised clients.'
+  spec.homepage      = 'http://ruby-hyperloop.org'
+  spec.license       = 'MIT'
+  # spec.metadata      = {
+  #   "homepage_uri" => 'http://ruby-hyperloop.org',
+  #   "source_code_uri" => 'https://github.com/ruby-hyperloop/hyper-component'
+  # }
 
-      # The following allow react code to be tested from the server side
-      s.add_development_dependency 'rspec-mocks'
-      s.add_development_dependency 'rspec-expectations'
-      s.add_development_dependency 'pry'
-      s.add_development_dependency 'pry-rescue'
-      s.add_development_dependency 'pry-stack_explorer'
+  spec.files          = `git ls-files`.split("\n").reject { |f| f.match(%r{^(examples|gemfiles|pkg|reactive_record_test_app|spec)/}) }
+  spec.executables    = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
+  spec.test_files     = `git ls-files -- {spec}/*`.split("\n")
+  spec.require_paths  = ['lib']
+  spec.post_install_message = "\033[0;31;1mhyper-mesh #{Hypermesh::VERSION} is in development and has know security issues! Not recommended for production use!\033[0;30;21m"
 
-      # s.add_development_dependency 'factory_girl_rails'
-      s.add_development_dependency 'shoulda'
-      s.add_development_dependency 'shoulda-matchers'
-      s.add_development_dependency 'rspec-its'
-      s.add_development_dependency 'rspec-collection_matchers'
-      s.add_development_dependency 'database_cleaner'
-      s.add_development_dependency 'capybara'
-      s.add_development_dependency 'selenium-webdriver', '< 3'
-      s.add_development_dependency 'poltergeist'
-      s.add_development_dependency 'spring-commands-rspec'
-      s.add_development_dependency 'chromedriver-helper'
-      s.add_development_dependency 'rspec-steps'
-      s.add_development_dependency 'parser'
-      s.add_development_dependency 'unparser'
-      s.add_development_dependency 'jquery-rails'
-      s.add_development_dependency 'pry-byebug'
-      s.add_development_dependency 'hyper-spec'
-      s.add_development_dependency 'hyper-trace'
-    end
+  spec.add_dependency 'activerecord', '>= 4.0.0'
+  spec.add_dependency 'hyper-component', Hypermesh::VERSION
+  spec.add_dependency 'hyper-operation', Hypermesh::VERSION
+  spec.add_development_dependency 'bundler'
+  spec.add_development_dependency 'capybara'
+  spec.add_development_dependency 'chromedriver-helper'
+  spec.add_development_dependency 'database_cleaner'
+  spec.add_development_dependency 'factory_bot_rails'
+  spec.add_development_dependency 'hyper-spec', Hypermesh::VERSION
+  spec.add_development_dependency 'hyper-trace'
+  spec.add_development_dependency 'mysql2'
+  spec.add_development_dependency 'opal-activesupport', '~> 0.3.1'
+  spec.add_development_dependency 'opal-browser', '~> 0.2.0'
+  spec.add_development_dependency 'opal-rails', '~> 0.9.3'
+  spec.add_development_dependency 'parser'
+  spec.add_development_dependency 'puma'
+  spec.add_development_dependency 'pusher'
+  spec.add_development_dependency 'pusher-fake'
+  spec.add_development_dependency 'rails', '>= 4.0.0'
+  spec.add_development_dependency 'rake'
+  spec.add_development_dependency 'react-rails', '>= 2.4.0', '< 2.5.0'
+  spec.add_development_dependency 'reactrb-rails-generator'
+  spec.add_development_dependency 'rspec-collection_matchers'
+  spec.add_development_dependency 'rspec-expectations'
+  spec.add_development_dependency 'rspec-its'
+  spec.add_development_dependency 'rspec-mocks'
+  spec.add_development_dependency 'rspec-rails'
+  spec.add_development_dependency 'rspec-steps', '~> 2.1.1'
+  spec.add_development_dependency 'rspec-wait'
+  spec.add_development_dependency 'rubocop', '~> 0.51.0'
+  spec.add_development_dependency 'shoulda'
+  spec.add_development_dependency 'shoulda-matchers'
+  spec.add_development_dependency 'spring-commands-rspec'
+  spec.add_development_dependency 'sqlite3'
+  spec.add_development_dependency 'mini_racer', '~> 0.1.15'
+  spec.add_development_dependency 'timecop', '~> 0.8.1'
+  spec.add_development_dependency 'unparser'
 end