best_in_place gem是否兼容Rails 6？无法编辑值该如何解决？

Absolutely, best_in_place does support Rails 6—but you’ll need to tweak a few configurations to get the edit functionality working, since Rails 6 introduced changes to JavaScript handling (like Webpacker as the default JS bundler) that break the gem’s out-of-the-box setup. Here’s a step-by-step solution that’s worked for me and many other developers:

1. Use a Rails 6-compatible version of the gem #

First, make sure you’re using a version of best_in_place updated for Rails 6. The official gem added Rails 6 support in version 3.1.0+, so update your Gemfile:

gem 'best_in_place', '>= 3.1.0'

Run bundle install to pull in the latest compatible version. If you still run into issues, try the GitHub main branch directly:

gem 'best_in_place', github: 'bernat/best_in_place'

2. Fix JavaScript dependencies (jQuery & UJS) #

Best_in_place relies on jQuery and jQuery UJS, which aren’t included by default in Rails 6. Here’s how to add them:

• Add jquery-rails to your Gemfile:

  gem 'jquery-rails'
  

• Run bundle install, then update your app/javascript/packs/application.js to import required libraries and initialize best_in_place:

  // Import jQuery and UJS
  import 'jquery'
  import 'jquery-ujs'
  // Import best_in_place
  import 'best_in_place'
  
  // Initialize best_in_place when the DOM is ready
  document.addEventListener('DOMContentLoaded', function() {
    jQuery('.best_in_place').best_in_place();
  });
  

3. Ensure your controller handles JS requests #

Best_in_place sends AJAX requests that expect a JavaScript response. Make sure your controller’s update action supports the js format. For example:

def update
  @user = User.find(params[:id])
  if @user.update(user_params)
    respond_to do |format|
      format.js { head :ok } # Minimal response confirming success
      format.html { redirect_to @user }
    end
  else
    respond_to do |format|
      format.js { head :unprocessable_entity }
      format.html { render :edit }
    end
  end
end

You don’t need a separate update.js.erb template unless you want custom behavior—head :ok is enough for the gem to refresh the displayed value.

4. Troubleshoot with browser dev tools #

If edits still don’t work, open your browser’s developer console (F12) and check for JavaScript errors:

• If you see $ is not defined, jQuery isn’t loading correctly—double-check your application.js imports.
• If best_in_place is not a function, the gem’s JS wasn’t imported properly.
• CSRF errors? jQuery UJS handles this automatically, but confirm your layout includes the csrf_meta_tags helper in the <head> section.

5. Verify your view syntax #

Double-check your best_in_place call in the view to ensure correct formatting. For example:

<%= best_in_place @user, :name, type: :input, placeholder: "Enter name" %>

Confirm the target model and attribute are correct, and the element has the best_in_place class (the helper adds this by default, but it’s worth verifying).

After following these steps, your best_in_place fields should display correctly and allow inline editing as expected.

内容的提问来源于stack exchange，提问作者Tomas