All Versions
30
Latest Version
Avg Release Cycle
65 days
Latest Release
99 days ago

Changelog History
Page 2

  • v2.1.1 Changes

    August 16, 2019

    🆕 New release (2.1.1) let's you toggle when render_async gets loaded on the page.

    By passing in a toggle hash, you can trigger render_async by clicking or doing other things to HTML elements.
    You can trigger render_async by doing something like this:

    <a href='#' id='detail-button'>detail</a>
    <%= render_async comments_path, toggle: { selector: '#detail-button', event: :click } %>
    

    This will trigger render_async to load when the user clicks the "detail" link on the page. render_async won't load until that event is triggered.

    🗄 DEPRECATION WARNING:

    If you've been using html_options as a second argument when calling render_async, you will have to change it to using a html_options hash like this:

    \<%= render\_async users\_path, html\_options: { nonce: 'lWaaV6eYicpt+oyOfcShYINsz0b70iR+Q1mohZqNaag=' } %\>
    
  • v2.1.0 Changes

    May 06, 2019

    🍱 Two new features come with 2.1.0 version! 🌮

    Retry on failure

    render_async can now retry on request failure for number of times you specify

    \<%= render\_async users\_path, retry\_count: 5, error\_message: "Users fetch has failed" %\>
    

    Closed #46

    Polling feature

    📊 You can now poll your paths and URLs by passing interval option to render_async

    \<%= render\_async comments\_path, interval: 5000 %\>
    

    This will fetch comments_path every 5 seconds. Closed #67 with this feature.

    POSSIBLE BREAKING CHANGE if you use this feature

    Container element is NOT being replaced like in other cases. This means that you will have to deal with render_async container element. There are ways of doing this by passing in an HTML element name and HTML element class.

  • v2.0.2 Changes

    January 04, 2019

    Locked bundler dependency was making problems to some users #73

    🚀 This release removes bundler from gemspec file and solves the issue.

  • v2.0.1 Changes

    December 10, 2018

    🔧 If you're using Turbolinks 5 or higher, you can resolve this by setting Turbolinks configurtion of render_async to true:

    RenderAsync.configure do |config| config.turbolinks = true # Enable this option if you are using Turbolinks 5+end
    

    This way, you're not breaking Turbolinks flow of loading or reloading a page.

    Also, invalid jQuery Promise method name has been replaced in this version.

  • v2.0.0 Changes

    October 06, 2018
  • v1.3.0 Changes

    October 06, 2018
  • v1.2.0 Changes

    January 25, 2018
  • v1.1.3 Changes

    November 23, 2017
    • #40: Replace render_async's container with the response data - @nikolalsvk.
  • v1.1.2 Changes

    November 17, 2017
  • v1.1.1 Changes

    October 14, 2017