blocks|key|1604805|text|对控制器使用复数名称只是一种惯例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1604806|复数名称通常听起来更自然(特别是对于直接绑定到特定模型的控制器:+User、->、Users等)，但您可以随心所欲地使用。|1604807|至于帮助器，默认情况下，所有的帮助器对所有控制器都是可用的，所以从技术上讲，如何命名你的帮助器一点也不重要。将控制器的帮助器函数保存在与控制器同名的帮助器中是另一种约定。|1604808|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Using plural names for controllers is just a convention.

Plural names usually sound more natural (especially for controllers that are tied directly to a specific model: User -> Users, etc.), but you can use whatever you want.

As for helpers, all helpers are available for all controllers by default, so technically, how you name your helpers doesn't matter at all. It's just another convention to keep a controller's helper functions in a helper with the same name as the controller.

blocks|key|1390021|text|使用复数听起来更好，然后如果你有一个控制器来处理单个资源，即用户，那么你仍然可以将url命名为/user。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390022|有了帮助器，通常不需要为每个控制器都有一个帮助器，而且经常会有一些帮助器方法，你可以在多个控制器中使用，而不是通过你的应用程序帮助器将它们全部丢弃。你可以把它们放在自定义的帮助器中，比如layout_helper或任何其他命名良好的文件。|1390023|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Using plurals just sounds better, and then if you have a controller that handles a singular resourse, ie user, then you can still name the url /user.

With helpers there is often no need to have a helper for every controller, and often there will be helper methods you can use ascorss multiple controllers and rather litter them all through your application helper you could put them in custom helpers instead like eg layout_helper or any other well named file.

blocks|key|1390076|text|当我使用单数作为控制器名称时，我感觉更好|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390077|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I feel better when I use singular for Controller name

blocks|key|1390138|text|模型是单数的，因为它引用了像用户这样的单个对象。控制器是复数，因为它是用于用户集合的控件(方法)。如何命名路由完全取决于单个开发人员。我从来没有遇到过用户抱怨web请求的URL是单数还是复数的。最终结果是为当前和未来的贡献者维护一个公共约定，同时为最终用户提供质量页面显示或API请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390139|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A Model is singular because it references a single object like User. A controller is plural because it is the controls (methods) for the collection of Users. How one names the routes is all up to that individual developer. I've never had a user complain that a URL for a web request is singular or plural. The end result to maintain a common convention for current and future contributors while serving quality page displays or the API requests for the end users.

blocks|key|1390204|text|在Rails指南中有一个非常完整的解释：http://edgeguides.rubyonrails.org/routing.html#resource-routing-the-rails-default|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1390205|entityMap|0|LINK|mutability|MUTABLE|url|http://edgeguides.rubyonrails.org/routing.html#resource-routing-the-rails-default^0|K|29|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You have a very complete explanation in the Rails guides:
<a href="http://edgeguides.rubyonrails.org/routing.html#resource-routing-the-rails-default" rel="noreferrer">http://edgeguides.rubyonrails.org/routing.html#resource-routing-the-rails-default</a>

blocks|key|1390281|text|这是Rails的约定，一个控制器处理一个模型，无论该模型的一个或多个实例在运行时是否存在。但是，您可以有一个Rails应用程序，其中(一些)控制器(和相关的视图)不与任何特定的模型相关联，而是处理一组更复杂的功能。在这种情况下，自动复数没有任何意义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390282|我目前正在开发的Rails应用程序就属于这一类，令我恼火的是，Rails期望我在一个地方定义为单数的标识符随后在其他地方以复数形式使用。例如，我可能想在config/routes.rb中定义如下内容|offset|length|style|CODE|1390283|++resource+:dashboard,+:only+=>+[:show]|code-block|syntax|javascript|1390284|然后，我希望控制器DashboardController显示有关应用程序某些方面的摘要信息，从多个数据库表中收集信息。因此，在这里，Dashboard并没有引用应用程序的任何模型，如果控制器的名称是DashboardsController，那就有点奇怪了。|1390285|我在this+answer中找到了一个很好的解决方案来解决自动多元化带来的困扰。简而言之，编辑文件config/initializers/inflections.rb，并将您不希望自动复数的单词添加到此定义中：|1390286|ActiveSupport::Inflector.inflections+do+%7Cinflect%7C
++inflect.uncountable+%25w(+dashboard+foo+bar+baz+)
end|1390287|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/6940226/351716^0|0|24|G|0|0|9|J|1U|9|2R|K|0|1D|Y|2|B|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|F|G]|$D|18|E|19|F|G]|$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|Q|3|R|5|J|7|1I|8|@]|9|@]|A|$K|L]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

It is the Rails convention that one controller handles one model, whether one or more instances of that model can exist during runtime. However, you can have a Rails application where (some of) the controllers (and the associated views) are not associated with any particular model, but rather handle a more complex set of functionality. In this case, the automatic pluralization doesn't make any sense.

The Rails application I'm currently working on fits into this category, and it's simply an irritation to me that Rails expects that the identifiers I define as a singular in one place are then used in their plural forms in other places. For example, I might want to define something like this in <code>config/routes.rb</code>:

<pre><code> resource :dashboard, :only =&gt; [:show]
</code></pre>

and then I want a controller <code>DashboardController</code> to display summary information about certain aspects of the application, gathering information from more than one database table. So here, <code>Dashboard</code> does not refer to any model of the application, and it would be just weird to have the controller's name be <code>DashboardsController</code>.

I found a good solution to the irritation of automatic pluralization in <a href="https://stackoverflow.com/a/6940226/351716">this answer</a>. In short, edit file <code>config/initializers/inflections.rb</code> and add the words you don't want to be automatically pluralized to this definition:

<pre><code>ActiveSupport::Inflector.inflections do |inflect|
 inflect.uncountable %w( dashboard foo bar baz )
end
</code></pre>

blocks|key|1605223|text|如果控制器是一个资源，那么它必须是复数...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605224|例如|1605225|控制器|1605226|articles_controller.rb|code-block|syntax|javascript|1605227|模型|1605228|article.rb|1605229|但是，当您没有相应的模型时，可以使用单数控制器名称|1605230|welcome_controller.rb|1605231|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

If the controller is a resource then it must be plural... 

For example 

Controller 

<pre><code>articles_controller.rb
</code></pre>

Model

<pre><code>article.rb
</code></pre>

But you can use singular controller names when you do not have corresponding models like 

<pre><code>welcome_controller.rb
</code></pre>

Is there any disadvantage to using singular names for controllers and helpers? Nothing seems to rely on this. It even seems helpers don't have to make the same choice about singular vs. plural as their corresponding controllers, at least according to my limited experimentation. Is that true?

Singular or plural controller and helper names in Rails

数据库

路由

对控制器和帮助器使用单数名称有什么缺点吗？似乎没有什么东西依赖于这一点。至少根据我有限的实验，似乎帮助者不必在单数和复数之间做出与其相应的控制器相同的选择。这是真的吗？

问Rails中的单数或复数控制器和帮助器名称
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rails中的单数或复数控制器和帮助器名称EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rails中的单数或复数控制器和帮助器名称
EN