我正在开发一个应用程序 有 1 个具有多对多关系的模块，它工作正常， 我可以用嵌套形式创建我的“单元”，但是当我处于编辑状态时我遇到了 1 个问题，当我点击提交按钮时它抛出了一个错误。
No route matches [POST] "/units/27"
i thought the action should be patch instead of post?? i inspect the generated html in browsers, and i can see there is a hidden field named "_method" with "patch" value.
我用脚手架生成了这个模块
单位模型
class Unit < ActiveRecord::Base
enum unitview: [ :city, :pool, :sea ]
enum furnish: [ "furnish", "non furnish", "semi furnish" ]
enum unitstatus: [ :draft, :publish, :unpublish, :waiting ]
belongs_to :apt
belongs_to :tower
belongs_to :room_type
belongs_to :template
belongs_to :floorplan
belongs_to :unitplan
validates :apt_id, presence: true
validates :tower_id, presence: true
validates :unitno, presence: true
validates :room_type_id, presence: true
validates :unitsize, presence: true
validates :unitfloor, presence: true
has_many :unitrentperiods, inverse_of: :unit
has_many :rentperiods, :through => :unitrentperiods
accepts_nested_attributes_for :unitrentperiods
end
租期模型
class Rentperiod < ActiveRecord::Base
validates :rentmonth, presence: true, numericality: { only_integer: true }
has_many :unitrentperiods, inverse_of: :rentperiod
has_many :units, :through => :unitrentperiods
end
单位租期模型
class Unitrentperiod < ActiveRecord::Base
belongs_to :unit ,inverse_of: :unitrentperiods
belongs_to :rentperiod ,inverse_of: :unitrentperiods
end
我不知道为什么，我的表单在创建模式下工作正常，但在编辑模式下却不行。
仅供引用，我试图删除我的嵌套表单，并且我的更新操作工作正常， 但是如果我放置我的嵌套表单，它会抛出路由错误。
为了让我的观点更容易阅读，这里是我的观点的简单版本
<%= form_for @unit, html: {class: "form-horizontal"} do |f| %>
<div class="form-group row">
<%= f.label 'Rent price', class: 'col-md-4 form-control-label' %>
<div class="col-md-8">
<table>
<%= f.fields_for :unitrentperiods do |elem| %>
<tr>
<td>
<%= elem.text_field :rentprice, class: 'col-md-4 form-control', name: "unit[unitrentperiods_attributes][][rentprice]" %> IDR
</td>
<td>
<%= elem.select :rentperiod_id, @rentperiods.map { |u| [u.rentmonth, u.id] }, { include_blank: true }, {:class => 'form-control', :name => 'unit[unitrentperiods_attributes][][rentperiod_id]'} %>
Month
</td>
</tr>
<% end -%>
</table>
</div>
</div>
<div class="form-group row">
<%= f.label 'Unit status', class: 'col-md-4 form-control-label' %>
<div class="col-md-8">
<%= f.select :unitstatus, options_for_select(@unit_statuses.collect { |s| [s[0].humanize, s[0]] }, selected: @unit.unitstatus), {} , class: "form-control" %>
</div>
</div>
<button type="submit" class="btn btn-sm btn-primary"><i class="fa fa-dot-circle-o"></i> Submit</button>
<% end %>
Controller
class UnitsController < ApplicationController
before_action :set_unit, only: [:show, :edit, :update, :destroy]
# GET /units
# GET /units.json
def index
@units = Unit.paginate(page: params[:page])
end
# GET /units/1
# GET /units/1.json
def show
end
def gettowers
tower = Tower.where(:apt_id => params[:apt_id])
@towers = tower.map{|a| [a.tower_name, a.id]}.insert(0, "Select a Tower")
end
def getfloorplans
floorplans = Floorplan.where(:apt_id => params[:apt_id]).select("id, floorplanphoto")
@imgs = floorplans
end
def getunitplans
unitplans = Unitplan.where(:apt_id => params[:apt_id]).select("id, unitplanphoto")
@imgs = unitplans
end
def preparedata
#master tables
@apts = Apt.all
@towers = Tower.all
@roomtypes = RoomType.all
@rentperiods = Rentperiod.all
array = []
Template.all.each do |t|
hash = { :type => t.room_type.room_type_desc, :id => t.id }
array.push(hash)
end
@templates = array
#enum from model
@unit_views = Unit.unitviews
@furnish_types = Unit.furnishes
@unit_statuses = Unit.unitstatuses
end
# GET /units/new
def new
@unit = Unit.new
preparedata
@rentperiods.each do |r|
@unit.unitrentperiods.build
end
end
# GET /units/1/edit
def edit
preparedata
end
# POST /units
# POST /units.json
def create
@unit = Unit.new(unit_params)
respond_to do |format|
if @unit.save
format.html { redirect_to unit_url, notice: 'Unit was successfully created.' }
format.json { render :show, status: :created, location: @unit }
else
format.html { render :new }
format.json { render json: @unit.errors, status: :unprocessable_entity }
end
end
end
# PATCH/PUT /units/1
# PATCH/PUT /units/1.json
def update
respond_to do |format|
if @unit.update(unit_params)
format.html { redirect_to unit_url, notice: 'Unit was successfully updated.' }
format.json { render :show, status: :ok, location: @unit }
else
format.html { render :edit }
format.json { render json: @unit.errors, status: :unprocessable_entity }
end
end
end
# DELETE /units/1
# DELETE /units/1.json
def destroy
@unit.destroy
respond_to do |format|
format.html { redirect_to units_url, notice: 'Unit was successfully destroyed.' }
format.json { head :no_content }
end
end
private
# Use callbacks to share common setup or constraints between actions.
def set_unit
@unit = Unit.find(params[:id])
end
# Never trust parameters from the scary internet, only allow the white list through.
def unit_params
params.require(:unit).permit(:apt_id, :tower_id, :unitno, :unitsize, :unitview,
:room_type_id, :unitfloor,
:unitdesc, :isforsell, :sellprice, :isforrent, :furnish, :totalbedroom,
:unitstatus, :template_id, :floorplan_id, :unitplan_id,
unitrentperiods_attributes: [ :rentprice, :rentperiod_id ])
end
end
路径文件
Rails.application.routes.draw do
resources :rentperiods
resources :pois
resources :towers
resources :apts
resources :areas
resources :regions
resources :contacts
resources :point_of_interest_types
resources :facilities
resources :room_types
resources :developers
resources :states
resources :countries
resources :unitplans, only: [:create, :destroy, :getunitplans]
resources :floorplans, only: [:create, :destroy, :getfloorplans]
resources :aptphotos, only: [:create, :destroy, :getphotos]
resources :templates
resources :templatephotos, only: [:create, :destroy, :getphotos]
get "units/gettowers"
get "units/getfloorplans"
get "units/getunitplans"
resources :units
post "templatephotos/create"
post "templatephotos/destroy"
get "templatephotos/getphotos"
post "unitplans/create"
post "unitplans/destroy"
get "unitplans/getunitplans"
post "floorplans/create"
post "floorplans/destroy"
get "floorplans/getfloorplans"
post "aptphotos/create"
post "aptphotos/destroy"
get "aptphotos/getphotos"
# The priority is based upon order of creation: first created -> highest priority.
# See how all your routes lay out with "rake routes".
# You can have the root of your site routed with "root"
root 'countries#index'
end
rake 路由输出:
pois#edit
poi GET /pois/:id(.:format)
pois#show
PATCH /pois/:id(.:format)
pois#update
PUT /pois/:id(.:format)
pois#update
DELETE /pois/:id(.:format)
pois#destroy
towers GET /towers(.:format)
towers#index
POST /towers(.:format)
towers#create
new_tower GET /towers/new(.:format)
towers#new
edit_tower GET /towers/:id/edit(.:format)
towers#edit
tower GET /towers/:id(.:format)
towers#show
PATCH /towers/:id(.:format)
towers#update
PUT /towers/:id(.:format)
towers#update
DELETE /towers/:id(.:format)
towers#destroy
apts GET /apts(.:format)
apts#index
POST /apts(.:format)
apts#create
new_apt GET /apts/new(.:format)
apts#new
edit_apt GET /apts/:id/edit(.:format)
apts#edit
apt GET /apts/:id(.:format)
apts#show
PATCH /apts/:id(.:format)
apts#update
PUT /apts/:id(.:format)
apts#update
DELETE /apts/:id(.:format)
apts#destroy
areas GET /areas(.:format)
areas#index
POST /areas(.:format)
areas#create
new_area GET /areas/new(.:format)
areas#new
edit_area GET /areas/:id/edit(.:format)
areas#edit
area GET /areas/:id(.:format)
areas#show
PATCH /areas/:id(.:format)
areas#update
PUT /areas/:id(.:format)
areas#update
DELETE /areas/:id(.:format)
areas#destroy
regions GET /regions(.:format)
regions#index
POST /regions(.:format)
regions#create
new_region GET /regions/new(.:format)
regions#new
edit_region GET /regions/:id/edit(.:format)
regions#edit
region GET /regions/:id(.:format)
regions#show
PATCH /regions/:id(.:format)
regions#update
PUT /regions/:id(.:format)
regions#update
DELETE /regions/:id(.:format)
regions#destroy
contacts GET /contacts(.:format)
contacts#index
POST /contacts(.:format)
contacts#create
new_contact GET /contacts/new(.:format)
contacts#new
edit_contact GET /contacts/:id/edit(.:format)
contacts#edit
contact GET /contacts/:id(.:format)
contacts#show
PATCH /contacts/:id(.:format)
contacts#update
PUT /contacts/:id(.:format)
contacts#update
DELETE /contacts/:id(.:format)
contacts#destroy
point_of_interest_types GET /point_of_interest_types(.:format)
point_of_interest_types#index
POST /point_of_interest_types(.:format)
point_of_interest_types#create
new_point_of_interest_type GET /point_of_interest_types/new(.:format)
point_of_interest_types#new
edit_point_of_interest_type GET /point_of_interest_types/:id/edit(.:forma
point_of_interest_types#edit
point_of_interest_type GET /point_of_interest_types/:id(.:format)
point_of_interest_types#show
PATCH /point_of_interest_types/:id(.:format)
point_of_interest_types#update
PUT /point_of_interest_types/:id(.:format)
point_of_interest_types#update
DELETE /point_of_interest_types/:id(.:format)
point_of_interest_types#destroy
facilities GET /facilities(.:format)
facilities#index
POST /facilities(.:format)
facilities#create
new_facility GET /facilities/new(.:format)
facilities#new
edit_facility GET /facilities/:id/edit(.:format)
facilities#edit
facility GET /facilities/:id(.:format)
facilities#show
PATCH /facilities/:id(.:format)
facilities#update
PUT /facilities/:id(.:format)
facilities#update
DELETE /facilities/:id(.:format)
facilities#destroy
room_types GET /room_types(.:format)
room_types#index
POST /room_types(.:format)
room_types#create
new_room_type GET /room_types/new(.:format)
room_types#new
edit_room_type GET /room_types/:id/edit(.:format)
room_types#edit
room_type GET /room_types/:id(.:format)
room_types#show
PATCH /room_types/:id(.:format)
room_types#update
PUT /room_types/:id(.:format)
room_types#update
DELETE /room_types/:id(.:format)
room_types#destroy
developers GET /developers(.:format)
developers#index
POST /developers(.:format)
developers#create
new_developer GET /developers/new(.:format)
developers#new
edit_developer GET /developers/:id/edit(.:format)
developers#edit
developer GET /developers/:id(.:format)
developers#show
PATCH /developers/:id(.:format)
developers#update
PUT /developers/:id(.:format)
developers#update
DELETE /developers/:id(.:format)
developers#destroy
states GET /states(.:format)
states#index
POST /states(.:format)
states#create
new_state GET /states/new(.:format)
states#new
edit_state GET /states/:id/edit(.:format)
states#edit
state GET /states/:id(.:format)
states#show
PATCH /states/:id(.:format)
states#update
PUT /states/:id(.:format)
states#update
DELETE /states/:id(.:format)
states#destroy
countries GET /countries(.:format)
countries#index
POST /countries(.:format)
countries#create
new_country GET /countries/new(.:format)
countries#new
edit_country GET /countries/:id/edit(.:format)
countries#edit
country GET /countries/:id(.:format)
countries#show
PATCH /countries/:id(.:format)
countries#update
PUT /countries/:id(.:format)
countries#update
DELETE /countries/:id(.:format)
countries#destroy
unitplans POST /unitplans(.:format)
unitplans#create
unitplan DELETE /unitplans/:id(.:format)
unitplans#destroy
floorplans POST /floorplans(.:format)
floorplans#create
floorplan DELETE /floorplans/:id(.:format)
floorplans#destroy
aptphotos POST /aptphotos(.:format)
aptphotos#create
aptphoto DELETE /aptphotos/:id(.:format)
aptphotos#destroy
templates GET /templates(.:format)
templates#index
POST /templates(.:format)
templates#create
new_template GET /templates/new(.:format)
templates#new
edit_template GET /templates/:id/edit(.:format)
templates#edit
template GET /templates/:id(.:format)
templates#show
PATCH /templates/:id(.:format)
templates#update
PUT /templates/:id(.:format)
templates#update
DELETE /templates/:id(.:format)
templates#destroy
templatephotos POST /templatephotos(.:format)
templatephotos#create
templatephoto DELETE /templatephotos/:id(.:format)
templatephotos#destroy
units_gettowers GET /units/gettowers(.:format)
units#gettowers
units_getfloorplans GET /units/getfloorplans(.:format)
units#getfloorplans
units_getunitplans GET /units/getunitplans(.:format)
units#getunitplans
unit_unitrentperiods GET /units/:unit_id/unitrentperiods(.:format)
unitrentperiods#index
POST /units/:unit_id/unitrentperiods(.:format)
unitrentperiods#create
new_unit_unitrentperiod GET /units/:unit_id/unitrentperiods/new(.:for
unitrentperiods#new
edit_unit_unitrentperiod GET /units/:unit_id/unitrentperiods/:id/edit(
rmat) unitrentperiods#edit
unit_unitrentperiod GET /units/:unit_id/unitrentperiods/:id(.:for
unitrentperiods#show
PATCH /units/:unit_id/unitrentperiods/:id(.:for
unitrentperiods#update
PUT /units/:unit_id/unitrentperiods/:id(.:for
unitrentperiods#update
DELETE /units/:unit_id/unitrentperiods/:id(.:for
unitrentperiods#destroy
units GET /units(.:format)
units#index
POST /units(.:format)
units#create
new_unit GET /units/new(.:format)
units#new
edit_unit GET /units/:id/edit(.:format)
units#edit
unit GET /units/:id(.:format)
units#show
PATCH /units/:id(.:format)
units#update
PUT /units/:id(.:format)
units#update
DELETE /units/:id(.:format)
units#destroy
templatephotos_create POST /templatephotos/create(.:format)
templatephotos#create
templatephotos_destroy POST /templatephotos/destroy(.:format)
templatephotos#destroy
templatephotos_getphotos GET /templatephotos/getphotos(.:format)
templatephotos#getphotos
unitplans_create POST /unitplans/create(.:format)
unitplans#create
unitplans_destroy POST /unitplans/destroy(.:format)
unitplans#destroy
unitplans_getunitplans GET /unitplans/getunitplans(.:format)
unitplans#getunitplans
floorplans_create POST /floorplans/create(.:format)
floorplans#create
floorplans_destroy POST /floorplans/destroy(.:format)
floorplans#destroy
floorplans_getfloorplans GET /floorplans/getfloorplans(.:format)
floorplans#getfloorplans
aptphotos_create POST /aptphotos/create(.:format)
aptphotos#create
aptphotos_destroy POST /aptphotos/destroy(.:format)
aptphotos#destroy
aptphotos_getphotos GET /aptphotos/getphotos(.:format)
aptphotos#getphotos
root GET /
countries#index
顺便说一句，我也试过像这样嵌套我的资源:
resources :units do
resources :unitrentperiods
end
仍然没有运气。
最佳答案
我找到了解决方案，以防其他人遇到同样的问题。在我原来的观点中，我把它放在我的嵌套形式中:
<%= elem.select :rentperiod_id,
@rentperiods.map { |u| [u.rentmonth, u.id] },
{ include_blank: true },
{:class => 'form-control', :name => 'unit[unitrentperiods_attributes][][rentperiod_id]'}
%>
为了解决这个问题，我删除了名称属性，还删除了路由文件中的嵌套资源。然后我将嵌套表单中的选择元素更改为:
<%= elem.select :rentperiod_id,
@rentperiods.map { |u| [u.rentmonth, u.id] },
{ include_blank: true },
{:class => 'form-control'}
%>
一切正常。
不过我还是不明白，为什么 name 属性会导致路由错误。
关于ruby-on-rails - 即使在编辑模式下，rails 嵌套形式始终为 "POST"？导致路由错误，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/39290644/
我正在学习如何使用Nokogiri，根据这段代码我遇到了一些问题:require'rubygems'require'mechanize'post_agent=WWW::Mechanize.newpost_page=post_agent.get('http://www.vbulletin.org/forum/showthread.php?t=230708')puts"\nabsolutepathwithtbodygivesnil"putspost_page.parser.xpath('/html/body/div/div/div/div/div/table/tbody/tr/td/div
总的来说，我对ruby还比较陌生，我正在为我正在创建的对象编写一些rspec测试用例。许多测试用例都非常基础，我只是想确保正确填充和返回值。我想知道是否有办法使用循环结构来执行此操作。不必为我要测试的每个方法都设置一个assertEquals。例如:describeitem,"TestingtheItem"doit"willhaveanullvaluetostart"doitem=Item.new#HereIcoulddotheitem.name.shouldbe_nil#thenIcoulddoitem.category.shouldbe_nilendend但我想要一些方法来使用
我有一个字符串input="maybe(thisis|thatwas)some((nice|ugly)(day|night)|(strange(weather|time)))"Ruby中解析该字符串的最佳方法是什么？我的意思是脚本应该能够像这样构建句子:maybethisissomeuglynightmaybethatwassomenicenightmaybethiswassomestrangetime等等，你明白了......我应该一个字符一个字符地读取字符串并构建一个带有堆栈的状态机来存储括号值以供以后计算，还是有更好的方法？也许为此目的准备了一个开箱即用的库？
我有一个Ruby程序，它使用rubyzip压缩XML文件的目录树。gem。我的问题是文件开始变得很重，我想提高压缩级别，因为压缩时间不是问题。我在rubyzipdocumentation中找不到一种为创建的ZIP文件指定压缩级别的方法。有人知道如何更改此设置吗？是否有另一个允许指定压缩级别的Ruby库？ 最佳答案 这是我通过查看rubyzip内部创建的代码。level=Zlib::BEST_COMPRESSIONZip::ZipOutputStream.open(zip_file)do|zip|Dir.glob("**/*")d
类classAprivatedeffooputs:fooendpublicdefbarputs:barendprivatedefzimputs:zimendprotecteddefdibputs:dibendendA的实例a=A.new测试a.foorescueputs:faila.barrescueputs:faila.zimrescueputs:faila.dibrescueputs:faila.gazrescueputs:fail测试输出failbarfailfailfail.发送测试[:foo,:bar,:zim,:dib,:gaz].each{|m|a.send(m)resc
很好奇，就使用rubyonrails自动化单元测试而言，你们正在做什么？您是否创建了一个脚本来在cron中运行rake作业并将结果邮寄给您？git中的预提交Hook？只是手动调用？我完全理解测试，但想知道在错误发生之前捕获错误的最佳实践是什么。让我们理所当然地认为测试本身是完美无缺的，并且可以正常工作。下一步是什么以确保他们在正确的时间将可能有害的结果传达给您？ 最佳答案 不确定您到底想听什么，但是有几个级别的自动代码库控制:在处理某项功能时，您可以使用类似autotest的内容获得关于哪些有效，哪些无效的即时反馈。要确保您的提
这似乎应该有一个直截了当的答案，但在Google上花了很多时间，所以我找不到它。这可能是缺少正确关键字的情况。在我的RoR应用程序中，我有几个模型共享一种特定类型的字符串属性，该属性具有特殊验证和其他功能。我能想到的最接近的类似示例是表示URL的字符串。这会导致模型中出现大量重复(甚至单元测试中会出现更多重复)，但我不确定如何让它更DRY。我能想到几个可能的方向...按照“validates_url_format_of”插件，但这只会让验证干给这个特殊的字符串它自己的模型，但这看起来很像重溶液为这个特殊的字符串创建一个ruby类，但是我如何得到ActiveRecord关联这个类模型
假设我做了一个模块如下:m=Module.newdoclassCendend三个问题:除了对m的引用之外，还有什么方法可以访问C和m中的其他内容？我可以在创建匿名模块后为其命名吗(就像我输入“module...”一样)？如何在使用完匿名模块后将其删除，使其定义的常量不再存在？ 最佳答案 三个答案:是的，使用ObjectSpace.此代码使c引用你的类(class)C不引用m:c=nilObjectSpace.each_object{|obj|c=objif(Class===objandobj.name=~/::C$/)}当然这取决于
我试图在一个项目中使用rake，如果我把所有东西都放到Rakefile中，它会很大并且很难读取/找到东西，所以我试着将每个命名空间放在lib/rake中它自己的文件中，我添加了这个到我的rake文件的顶部:Dir['#{File.dirname(__FILE__)}/lib/rake/*.rake'].map{|f|requiref}它加载文件没问题，但没有任务。我现在只有一个.rake文件作为测试，名为“servers.rake”，它看起来像这样:namespace:serverdotask:testdoputs"test"endend所以当我运行rakeserver:testid时
出于纯粹的兴趣，我很好奇如何按顺序创建PI，而不是在过程结果之后生成数字，而是让数字在过程本身生成时显示。如果是这种情况，那么数字可以自行产生，我可以对以前看到的数字实现垃圾收集，从而创建一个无限系列。结果只是在Pi系列之后每秒生成一个数字。这是我通过互联网筛选的结果:这是流行的计算机友好算法，类机器算法:defarccot(x,unity)xpow=unity/xn=1sign=1sum=0loopdoterm=xpow/nbreakifterm==0sum+=sign*(xpow/n)xpow/=x*xn+=2sign=-signendsumenddefcalc_pi(digits