Added EnsureAssetsCompiled feature so that you do not accidentally run tests without properly compiling the JavaScript bundles. Add a line to your rails_helper.rb file to check that the latest Webpack bundles have been generated prior to running tests that may depend on your client-side code. See docs for more detailed instructions. #222
Added migration guide for migrating from React-Rails. #219
Added React on Rails Doctrine to docs. Discusses the project's motivations, conventions, and principles. #220
Added ability to skip display:none style in the generated content tag for a component. Some developers may want to disable inline styles for security reasons. See generated config initializer file for example on setting skip_display_none. #218

Fixed handling of Turbolinks. Code was checking that Turbolinks was installed when it was not yet because some setups load Turbolinks after the bundles. The changes to the code will check if Turbolinks is installed after the page loaded event fires. Code was also added to allow easy debugging of Turbolinks, which should be useful when v5 of Turbolinks is released shortly. Details of how to configure Turbolinks with troubleshooting were added to docs directory. #221
Fixed issue with already initialized constant warning appearing when starting a Rails server #226
Fixed to make backwards compatible with Ruby v2.0 and updated all Ruby and Node dependencies.

2.0.2

published 2.0.2 • 9 years ago

Changelog

2.0.1

published 2.0.1 • 9 years ago

Changelog

published 2.0.0 • 9 years ago

Changelog

Move JavaScript part of react_on_rails to npm package 'react-on-rails'.
Converted JavaScript code to ES6! with tests!
No global namespace pollution. ReactOnRails is the only global added.
New API. Instead of placing React components on the global namespace, you instead call ReactOnRails.register, passing an object where keys are the names of your components:

import ReactOnRails from 'react-on-rails';
ReactOnRails.register({name: component});

Best done with Object destructing:

  import ReactOnRails from 'react-on-rails';
  ReactOnRails.register(
    {
      Component1,
      Component2
    }
  );

Previously, you used

window.Component1 = Component1;
window.Component2 = Component2;

This would pollute the global namespace. See details in the README.md for more information.

  ReactOnRails.render(componentName, props, domNodeId);

such as:

  ReactOnRails.render("HelloWorldApp", {name: "Stranger"}, 'app');

All npm dependency libraries updated. Most notable is going to Babel 6.
Dropped support for react 0.13.
JS Linter uses ShakaCode JavaScript style: https://github.com/shakacode/style-guide-javascript
Generators account these differences.

Update the react_on_rails gem.
Remove //= require react_on_rails from any files such as app/assets/javascripts/application.js. This file comes from npm now.
Search you app for 'generator_function' and remove lines in layouts and rb files that contain it. Determination of a generator function is handled automatically.
Find your files where you registered client and server globals, and use the new ReactOnRails.register syntax. Optionally rename the files clientRegistration.jsx and serverRegistration.jsx rather than Globals.
Update your index.jade to use the new API ReactOnRails.render("MyApp", !{props}, 'app');
Update your webpack files per the example commit. Remove globally exposing React and ReactDom, as well as their inclusion in the entry section. These are automatically included now.
Run cd client && npm i --save react-on-rails to get react-on-rails into your client/package.json.
You should also update any other dependencies if possible to match up with the react-webpack-rails-tutorial. This includes updating to Babel 6.
If you want to stick with Babel 5 for a bit, see Issue #238.