我正在创建一个名为员工管理系统的应用程序Rails 7。为了添加员工，我创建了一个表单。在这里，我使用nested-form-fields gem 来添加员工的联系人。问题是当第一次加载表单时，当我想添加或删除联系人字段时，它会重定向到同一表单。但是当我刷新页面时，它就开始工作，没有任何问题。即使添加或删除的字段也会反映在数据库中。仅在首次加载创建或更新员工页面时才会出现此问题。 我发现当我单击添加员工的链接时，表单将打开。事件不会以 html 形式加载。正如我们在下图中靠近 body 标签所看到的：
But after refresh, events are loaded:
我在 gem 文件夹中看到了 js.coffee 文件，但这对于像我这样的初学者来说太高级了。那里的代码看起来像这样：
window.nested_form_fields or= {}
nested_form_fields.bind_nested_forms_links = () ->
$('body').off("click", '.add_nested_fields_link')
$('body').on 'click', '.add_nested_fields_link', (event, additional_data) ->
$link = $(this)
object_class = $link.data('object-class')
association_path = $link.data('association-path')
added_index = $(".nested_#{association_path}").length
$.event.trigger("fields_adding.nested_form_fields",{object_class: object_class, added_index: added_index, association_path: association_path, additional_data: additional_data});
if $link.data('scope')
$template = $("#{$link.data('scope')} ##{association_path}_template")
else
$template = $("##{association_path}_template")
target = $link.data('insert-into')
template_html = $template.html()
# insert association indexes
index_placeholder = "__#{association_path}_index__"
template_html = template_html.replace(new RegExp(index_placeholder,"g"), added_index)
# look for replacements in user defined code and substitute with the index
template_html = template_html.replace(new RegExp("__nested_field_for_replace_with_index__","g"), added_index)
# replace child template div tags with script tags to avoid form submission of templates
$parsed_template = $(template_html)
$child_templates = $parsed_template.closestChild('.form_template')
$child_templates.each () ->
$child = $(this)
$child.replaceWith($("<script id='#{$child.attr('id')}' type='text/html' />").html($child.html()))
if target?
$('#' + target).append($parsed_template)
else
$template.before( $parsed_template )
$parsed_template.trigger("fields_added.nested_form_fields", {object_class: object_class, added_index: added_index, association_path: association_path, event: event, additional_data: additional_data});
false
$('body').off("click", '.remove_nested_fields_link')
$('body').on 'click', '.remove_nested_fields_link', ->
$link = $(this)
return false unless $.rails == undefined || $.rails.allowAction($link)
return false if $link.attr('disabled')
object_class = $link.data('object-class')
delete_association_field_name = $link.data('delete-association-field-name')
removed_index = parseInt(delete_association_field_name.match('(\\d+\\]\\[_destroy])')[0].match('\\d+')[0])
$.event.trigger("fields_removing.nested_form_fields",{object_class: object_class, delete_association_field_name: delete_association_field_name, removed_index: removed_index });
$nested_fields_container = $link.parents(".nested_fields").first()
delete_field = $nested_fields_container.find("input[type='hidden'][name='#{delete_association_field_name}']")
if delete_field.length > 0
delete_field.val('1')
else
$nested_fields_container.before "<input type='hidden' name='#{delete_association_field_name}' value='1' />"
$nested_fields_container.hide()
$nested_fields_container.find('input[required]:hidden, select[required]:hidden, textarea[required]:hidden').removeAttr('required')
$nested_fields_container.trigger("fields_removed.nested_form_fields",{object_class: object_class, delete_association_field_name: delete_association_field_name, removed_index: removed_index});
false
$(document).on "page:change turbolinks:load", ->
nested_form_fields.bind_nested_forms_links()
jQuery ->
nested_form_fields.bind_nested_forms_links()
#
# * jquery.closestchild 0.1.1
# *
# * Author: Andrey Mikhaylov aka lolmaus
# * Email: [email protected] /cdn-cgi/l/email-protection
# *
#
$.fn.closestChild = (selector) ->
$children = undefined
$results = undefined
$children = @children()
return $() if $children.length is 0
$results = $children.filter(selector)
if $results.length > 0
$results
else
$children.closestChild selector有什么可以改变的来解决这个问题吗？请帮忙！！
在我的应用程序上工作了 2 天后，当我将 jquery 添加到 application.js 以添加一个使永久地址和本地地址相同的复选框时，出现了同样的问题。所以我得出的结论是，问题不是因为 gem 而是因为其他原因。所以我用谷歌搜索，发现turbolink是罪魁祸首。在turbo-rails github存储库中搜索后，在“已关闭”类别中发现了该问题。通过在 application.html.erb 的 head 部分添加一个简单的行，了解了该问题。线路是：
<meta name="turbo-visit-control" content="reload">
不过，有一个问题。添加此行后，闪烁消息因重新加载而消失。于是我又去google了一下，希望找到更好的方法。删除了这一行，并在 application.js 中进行了更改
import "@hotwired/turbo-rails"
to
import { Turbo } from "@hotwired/turbo-rails"
Turbo.session.drive = false`
这是我在涡轮导轨中发现的自述文件.md https://github.com/hotwired/turbo-rails#navigate-with-turbo-drive。 并且无需刷新页面即可重新出现闪现消息。