blocks|key|1975831|text|您可以使用:symbol作为第一个参数。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1975832|<%25=+simple_form_for+:user,+url:+users_path+do+%7Cf%7C+%25>
++<%25=+f.input+:name,+as:+:string+%25>
++...
<%25+end+%25>|code-block|syntax|javascript|1975833|它将输出类似如下的内容：|1975834|<form+novalidate="novalidate"+class="simple_form+user"+action="/users"+accept-charset="UTF-8"+method="post">
++...
++<div+class="input+string+required+user_name">
++++<label+class="string+required"+for="user_name">
++++++<abbr+title="required">*</abbr>+Name
++++</label>
++++<input+class="string+required"+type="text"+name="user[name]"+id="user_name"+/>
++</div>
++...
</form>|1975835|entityMap^0|5|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

<p>You can use <code>:symbol</code> as the first argument.</p>

<pre><code>&lt;%= simple_form_for :user, url: users_path do |f| %&gt;
  &lt;%= f.input :name, as: :string %&gt;
  ...
&lt;% end %&gt;
</code></pre>

<p>It will output something like this:</p>

<pre><code>&lt;form novalidate="novalidate" class="simple_form user" action="/users" accept-charset="UTF-8" method="post"&gt;
  ...
  &lt;div class="input string required user_name"&gt;
    &lt;label class="string required" for="user_name"&gt;
      &lt;abbr title="required"&gt;*&lt;/abbr&gt; Name
    &lt;/label&gt;
    &lt;input class="string required" type="text" name="user[name]" id="user_name" /&gt;
  &lt;/div&gt;
  ...
&lt;/form&gt;
</code></pre>


blocks|key|3311859|text|不幸的是，simple_form依赖于使用模型。从本质上讲，如果有类似于simple_form_tag和input_tag方法的东西与它们的rails+*_tag帮助器等同，那就更好了。在此之前，有一个简单的解决办法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3311860|在表单中使用符号而不是类，并显式传递该值以防止simple_form尝试访问模型属性。|3311861|<%25=+simple_form_for+:user,+:url+=>+'/users'+do+%7Cf%7C+%25>
++<%25=+f.text_field+:name,+input_html:+{+value:+nil+}+%25>
<%25+end+%25>|code-block|syntax|javascript|3311862|这将避免undefined+method+'name'+for+User错误。|offset|length|style|CODE|3311863|entityMap^0|0|0|0|4|W|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

<p>Unfortunately simple_form relies on using a model. Essentially it would be nice to have something like simple_form_tag and input_tag methods equivalent to their rails *_tag helpers. Until then, there's an easy work around. </p>

<p>Use a symbol instead of the class in the form and pass the value explicitly to prevent simple_form from trying to access the model properties. </p>

<pre><code>&lt;%= simple_form_for :user, :url =&gt; '/users' do |f| %&gt;
  &lt;%= f.text_field :name, input_html: { value: nil } %&gt;
&lt;% end %&gt;
</code></pre>

<p>This will avoid the <code>undefined method 'name' for User</code> error.</p>


blocks|key|3311918|text|您还可以在表单模型中使用模型外部的字段，simple_fields_for如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3311919|<%25=+simple_form_for+@user+do+%7Cf%7C+%25>
++<%25=+f.input+:name+%25>

++<%25=+simple_fields_for+:no_model_fields+do+%7Cn%7C+%25>
++++<%25=+n.input+:other_field+%25>
++<%25+end+%25>
<%25+end+%25>|code-block|syntax|javascript|3311920|这是一个简单而实用的解决方案，因为您可以从不同的模型创建不同类型的字段，也可以不使用模型|3311921|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

<p>You can also use fields outside the model within a form model, with simple_fields_for like this:</p>

<pre><code>&lt;%= simple_form_for @user do |f| %&gt;
  &lt;%= f.input :name %&gt;

  &lt;%= simple_fields_for :no_model_fields do |n| %&gt;
    &lt;%= n.input :other_field %&gt;
  &lt;% end %&gt;
&lt;% end %&gt;
</code></pre>

<p>This is simple and practical solution, because you can create different kind of fields from different models or without  using models</p>


blocks|key|4912077|text|您还可以传递:symbol而不是@object作为simple_form_for的参数。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4912078|<%25=+simple_form_for+:email,+:url+=>+'/post_email'+do+%7Cf%7C+%25>
++<%25=+f.input+:subject,+:as+=>+:string+%25>
<%25+end+%25>|code-block|syntax|javascript|4912079|这将输出：|4912080|<form+method="post"+class="simple_form+email"+action="/post_email"+accept-charset="UTF-8">
++...
++<input+type="text"+size="30"+name="email[subject]"+id="email_subject">
</form>|4912081|请注意以下回调：|4912082|您将无法利用自动模型validation|4912083|Need来显式定义每个input|unordered-list-item|4912084|
的类型和|4912085|4912086|4912087|entityMap^0|6|7|G|7|P|F|0|0|0|0|0|0|B|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|19|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1B|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1C|8|@]|D|@]|E|$]]|$1|S|3|T|5|U|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1G|8|@]|D|@]|E|$]]|$1|X|3|-4|5|U|7|1H|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|10|$]]

<p>You could also pass a <code>:symbol</code> instead of <code>@object</code> as argument for <code>simple_form_for</code>.</p>

<pre><code>&lt;%= simple_form_for :email, :url =&gt; '/post_email' do |f| %&gt;
  &lt;%= f.input :subject, :as =&gt; :string %&gt;
&lt;% end %&gt;
</code></pre>

<p>Which would output:</p>

<pre><code>&lt;form method="post" class="simple_form email" action="/post_email" accept-charset="UTF-8"&gt;
  ...
  &lt;input type="text" size="30" name="email[subject]" id="email_subject"&gt;
&lt;/form&gt;
</code></pre>

<p>Please be aware of following draw-backs:</p>

<ul>
<li>You won't be able to take advantage of automatic model validation</li>
<li>Need to explicitly define <code>:url</code> and the type of each <code>input</code></li>
</ul>


blocks|key|4912156|text|上面的所有方法仍然会给您留下嵌套在"user“或您作为第一个参数传递的任何符号中的表单数据。这太烦人了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4912157|要模仿simple_form的样式/优点，但要移除对象/符号依赖和强制数据嵌套，您可以创建一个部分。|4912158|HAML示例：|offset|length|style|CODE|4912159|表单视图：|4912160|=+form_tag("path/to/action",+method:+"POST")+do
++++=+render+"path/to/partial/field",+type:+"string",+required:+true,+item:+"first_name"|code-block|syntax|javascript|4912161|field部分：|4912162|-+required_string+=+required+?+"required"+:+""
%25div{class:+"input+#{type}+#{required_string}+#{item}"}
++%25label{class:+"#{type}+#{required_string}",+for:+"#{item}"}
++++-+if+required
++++++%25abbr{title:+"required"}
++++++++*
++++=+t("application.#{item}")
++%25input{name:+"#{item}",+++++++++++++++++++++++++++++++++++++++++++++++++++++%7C
++++placeholder:+t("application.#{item}"),++++++++++++++++++++++++++++++++++++%7C
++++type:+"#{type}",++++++++++++++++++++++++++++++++++++++++++++++++++++++++++%7C
++++required:+required,+++++++++++++++++++++++++++++++++++++++++++++++++++++++%7C
++++"aria-required"+=>+"#{required}"+}|4912163|entityMap^0|0|0|0|4|0|0|0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@$F|Z|G|10|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|12|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|13|8|@$F|14|G|15|H|I]]|9|@]|A|$]]|$1|S|3|T|5|N|7|16|8|@]|9|@]|A|$O|P]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

<p>All of the methods above still leave you with form data nested inside of "user" or whatever symbol that you pass as the first argument.  That's annoying.</p>

<p>To mimic simple_form's style/benefits, but remove the object/symbol dependency and the forced data nesting, you can create a partial.</p>

<p><code>HAML</code> examples:</p>

<p>form view:</p>

<pre><code>= form_tag("path/to/action", method: "POST") do
    = render "path/to/partial/field", type: "string", required: true, item: "first_name"
</code></pre>

<p><code>field</code> partial:</p>

<pre><code>- required_string = required ? "required" : ""
%div{class: "input #{type} #{required_string} #{item}"}
  %label{class: "#{type} #{required_string}", for: "#{item}"}
    - if required
      %abbr{title: "required"}
        *
    = t("application.#{item}")
  %input{name: "#{item}",                                                     |
    placeholder: t("application.#{item}"),                                    |
    type: "#{type}",                                                          |
    required: required,                                                       |
    "aria-required" =&gt; "#{required}" }
</code></pre>


<p>Is it possible to use Simple Form (by: Plataformatec) without a model?</p>

<p><a href="https://github.com/plataformatec/simple_form" rel="noreferrer">https://github.com/plataformatec/simple_form</a></p>


SimpleForm without for (non model form)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

可以在没有模型的情况下使用Simple Form (by: Plataformatec)吗？

问不带for的SimpleForm (非模型表单)
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不带for的SimpleForm (非模型表单)EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不带for的SimpleForm (非模型表单)
EN