Reactrb changelog

Changelog History

Page 2

• v0.9.0 Changes

  October 19, 2016

  ➕ Added

  • react/react-source is the suggested way to include ReactJS sources now. Simply require react/react-source immediately before the require "reactrb" in your Opal code will make it work.

  🗄 Deprecated

  • ✅ react-latest & react-v1x is deprecated. Use react/react-source instead.

  ✂ Removed

  • 🚚 opal-browser is removed from runtime dependency. (#133) You will have to add gem 'opal-browser' to your gemfile (recommended) or remove all references to opal-browser from your manifest files.

  🛠 Fixed

  • $window#on in opal-jquery is broken. (#166)
  • Element#render trigger unnecessary re-mounts when called multiple times. (#170)
  • ⚡️ Gets rid of react warnings about updating state during render (#155)
  • Multiple HAML classes (i.e. div.foo.bar) was not working (regression introduced in 0.8.8)
  • Don't send nil (null) to form components as the value string (#157)
  • 🖨 Process params (props) correctly when using Element#on or Element#render (#158)
  • 🗄 Deprecate shallow param compare (#156)

• v0.8.8 Changes

  July 13, 2016

  ➕ Added

  • More helpful error messages on render failures (#152)
  • Element#on('<my_event_name>') subscribes to my_event_name (#153)

  🔄 Changed

  • Element#on(:event) subscribes to on_event for reactrb components and onEvent for native components. (#153)

  🗄 Deprecated

  • 🗄 Element#on(:event) subscription to _onEvent is deprecated. Once you have changed params named _on... to on_... you can require 'reactrb/new-event-name-convention.rb' to avoid spurious react warning messages. (#153)

  🛠 Fixed

  • The Element['#container'].render... method generates a spurious react error (#154)

• v0.8.7 Changes

  July 08, 2016

  🛠 Fixed

  • Opal 0.10.x compatibility

• v0.8.6 Changes

  June 30, 2016

  🛠 Fixed

  • Method missing within a component was being reported as incorrect const name (#151)

• « First
• ‹ Prev
• 1
• 2