用于创建嵌套资源实例的表单

发布于 2024-11-09 04:02:09 字数 669 浏览 0 评论 0原文

如何在父模型之外创建关联的模型实例？

我有一个嵌套资源

# config/routes.rb
resources :users do
    resources :messages
end

# models/user.rb
has_many :messages
# some other user model specifications

# models/messages.rb
belongs_to :user

，我遵循 RailsTutorial.org 中引入的身份验证程序；所以我有一个名为 current_user 的帮助程序，它返回已登录的用户。此方法位于 ApplicationController 中包含的 SessionsHelper 模块中

# views/messages/new
= form_for current_user.messages.build do |f|

。视图中会输出错误

undefined method 'messages_path' for #<#<Class:0xHex_Number>:0xHex_Number

这个想法是允许用户在彼此之间发送消息。

原文

How does one go about creating an associated model instance outside the parent model?

I have a nested resource

# config/routes.rb
resources :users do
    resources :messages
end

# models/user.rb
has_many :messages
# some other user model specifications

# models/messages.rb
belongs_to :user

I followed the authentication procedures introduced in RailsTutorial.org; so I have a helper called current_user that returns the user that is signed in. This method is in a SessionsHelper module included in the ApplicationController

# views/messages/new
= form_for current_user.messages.build do |f|

This line in the view spits out an error

undefined method 'messages_path' for #<#<Class:0xHex_Number>:0xHex_Number

The idea is to allow users send messages amongst themselves.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

九八野马 2024-11-16 04:02:09

我通过在视图中构建占位符消息解决了视图层错误。

= form_for current_user.messages.build, :url new_user_message_path(:user_id => current_user do |f|

这使得可以呈现表单，但是当我提交表单时，浏览器向 new 操作发送了一个 POST 请求。控制台日志显示...

Started POST "/users/1/messages/new" for 127.0.0.1 at ...

ActionController::RoutingError (No route matches "/users/1/messages/new"):

...这显然是错误的。根据 REST 理论，接收 get 请求的函数不应响应 POST 请求，即函数应该是特定于请求的。

为了解决这个问题，我更改了以下内容：

# controllers/messages
   def new
++   @message = Message.new
   end

# views/messages/new
-- form_for current_user.messages.build, :url new_user_message_path(:user_id => current_user do |f|
++ form_for [current_user, @message] do |f|

这样，在提交时，创建函数会收到 POST 请求。在控制台中...

Started POST "/users/1/messages" for 127.0.0.1 at ...
  Processing by MessagesController#create as HTML
  Parameters: {"authenticity_token"=>"areallylongstringthatnobodycanguess", "utf8"=>"✓", "message"=>{"title"=>"This is a breakthrough", "recipient"=>"Jamie", "content"=>"can you believe the developers got the messaging system working???"}, "user_id"=>"1"}
Completed   in 5ms

...正如预期的那样。

I solved the view layer error by building a placeholder message in the view.

= form_for current_user.messages.build, :url new_user_message_path(:user_id => current_user do |f|

This enabled a form to be rendered but when I submitted the form, the browser sent a POST request to the new action. The console log read...

Started POST "/users/1/messages/new" for 127.0.0.1 at ...

ActionController::RoutingError (No route matches "/users/1/messages/new"):

...which is obviously wrong. According to the REST theory, a function that receives a get request should not respond to a POST request i.e. functions should be request-specific.

To fix this, I changed the following:

# controllers/messages
   def new
++   @message = Message.new
   end

# views/messages/new
-- form_for current_user.messages.build, :url new_user_message_path(:user_id => current_user do |f|
++ form_for [current_user, @message] do |f|

This way, on submission, the create function receives a POST request. In the console...

Started POST "/users/1/messages" for 127.0.0.1 at ...
  Processing by MessagesController#create as HTML
  Parameters: {"authenticity_token"=>"areallylongstringthatnobodycanguess", "utf8"=>"✓", "message"=>{"title"=>"This is a breakthrough", "recipient"=>"Jamie", "content"=>"can you believe the developers got the messaging system working???"}, "user_id"=>"1"}
Completed   in 5ms

...as expected.

回复收藏 0 原文

~没有更多了~