All Versions
130
Latest Version
Avg Release Cycle
61 days
Latest Release
951 days ago
Changelog History
Page 13
Changelog History
Page 13
-
v2.3.0 Changes
February 01, 2016โ Added
- โ Added polyfills for
setInterval
andsetTimeout
in case other libraries expect these to exist. - โ Added much improved debugging for errors in the server JavaScript webpack file.
- See #244 for these improvements.
- โ Added polyfills for
-
v2.2.0 Changes
January 29, 2016โ Added
- ๐ New JavaScript API for debugging TurboLinks issues. Be sure to see turbolinks docs.
ReactOnRails.setOptions({ traceTurbolinks: true });
. Removed the filedebug_turbolinks
added in 2.1.1. See #243.
- ๐ New JavaScript API for debugging TurboLinks issues. Be sure to see turbolinks docs.
-
v2.1.1 Changes
January 28, 2016๐ Fixed
- ๐ Fixed regression where apps that were not using Turbolinks would not render components on page load.
โ Added
ReactOnRails.render
returns a virtualDomElement Reference to your React component's backing instance. See #234.- ๐
debug_turbolinks
helper for debugging turbolinks issues. See turbolinks. - โจ Enhanced regression testing for non-turbolinks apps. Runs all tests for dummy app with turbolinks both disabled and enabled.
-
v2.1.0 Changes
January 26, 2016โ Added
- ๐ 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](lib/generators/react_on_rails/templates/base/base/config/initializers/react_on_rails.rb#L27) for example on settingskip_display_none
. #218
๐ Changed
- Changed message when running the dev (a.k.a. "express" server). #227
๐ Fixed
- 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.
- ๐ Added EnsureAssetsCompiled feature so that you do not accidentally run tests without properly compiling the JavaScript bundles. Add a line to your
-
v2.0.2 Changes
- Added better messages after generator runs. #210
-
v2.0.1 Changes
- ๐ Fixed bug with version matching between gem and npm package.
-
v2.0.0 Changes
- 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 usedwindow.Component1 = Component1; window.Component2 = Component2;
This would pollute the global namespace. See details in the README.md for more information. - Your jade template for the WebpackDevServer setup should use the new API:
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.
Migration Steps v1 to v2
โฌ๏ธ Example of upgrading
- Update the
react_on_rails
gem. - Remove
//= require react_on_rails
from any files such asapp/assets/javascripts/application.js
. This file comes from npm now. ๐ 3. 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. ๐ 4. Find your files where you registered client and server globals, and use the new ReactOnRails.register syntax. Optionally rename the filesclientRegistration.jsx
andserverRegistration.jsx
rather thanGlobals
. โก๏ธ 5. Update your index.jade to use the new APIReactOnRails.render("MyApp", !{props}, 'app');
โก๏ธ 6. Update your webpack files per the example commit. Remove globally exposing React and ReactDom, as well as their inclusion in theentry
section. These are automatically included now. ๐ฆ 7. Runcd client && npm i --save react-on-rails
to get react-on-rails into yourclient/package.json
. โก๏ธ 8. 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.
-
v1.2.0 Changes
โ Added
- ๐ Support
--skip-bootstrap
or-b
option for generator. - โ Create examples tasks to test generated example apps.
๐ Fixed
- ๐ Fix non-server rendering configuration issues.
- ๐ Fix application.js incorrect overwritten issue.
- ๐ Fix Gemfile dependencies.
- ๐ Fix several generator issues.
โ Removed
- โ Removed templates/client folder.
- ๐ Support
-
v1.1.1 Changes
November 28, 2015โ Added
- ๐ Support for React Router.
- Error and redirect handling.
- ๐ Turbolinks support.
๐ Fixed
- ๐ Fix several generator related issues.