All Versions
12
Latest Version
Avg Release Cycle
128 days
Latest Release
952 days ago

Changelog History
Page 1

  • v0.3.2 Changes

    March 16, 2019
    • Gracefully handle nil templates
      🚅 #96
  • v0.3.1 Changes

    June 16, 2017
    • Include xray.js when using jQuery3
      🚅 #84
  • v0.3.0 Changes

    April 28, 2017
    • Remove alias_method_chain and make xray-rails compatible with Rails 5.1.
  • v0.2.0 Changes

    September 23, 2016
    • ✂ Removed support for Backbone-rendered templates. This feature was particularly
      complex and prone to failure. It will more than likely return in some form in
      ⬆️ the future - for now, if your workflow depends on it, don't upgrade to 0.2.0.
    • ✂ Removed the dependency on coffee-rails.
    • 🛠 Fixed deprecation warnings from Sprockets 4.
  • v0.1.23 Changes

    September 23, 2016
    • ➕ Add a post-install message regarding future removal of Backbone support.
  • v0.1.22 Changes

    September 08, 2016
    • 0️⃣ If you have not explicitly set an editor, xray-rails now chooses a default
      editor by using the following environment variables: GEM_EDITOR, VISUAL,
      and EDITOR. To explicitly set the editor, use ~/.xrayconfig as explained
      🔧 in the configuration section
      of the README.
  • v0.1.21 Changes

    May 21, 2016
    • 🛠 Fix a regression in 0.1.20 that broke Rails 3.2 apps
      🚅 #72
  • v0.1.20 Changes

    May 18, 2016
    • ➕ Added support for Rails 5.0.0.rc1.
      🚅 #70
  • v0.1.19 Changes

    May 06, 2016
    • 🚀 Previous releases of xray-rails had a file permissions issue that caused a
      "can't load lib/xray/middleware" error on some systems. This should now be
      🛠 fixed. #59
    • 🚅 The xray-rails JavaScript is now properly injected after jquery2. This means
      🚅 that projects using jQuery2 should now work with xray-rails out of the box.
      🚅 #64 @nextekcarl
  • v0.1.18 Changes

    May 06, 2016
    • 🚅 xray-rails is now compatible with sprockets-rails 3.0
      🚅 #62 @mattbrictson