You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Didn't see this documented anywhere, and just wanted to raise this for visibility in case anyone is upgrading from 0.9.x to 0.10.x and is running into this error.
There was some logic added to the destroy method in the 0.10.0 release that uses the referrer on the request to add a turbo stream response when a resource is deleted. If you don't include a referrer on the request, you'll get the ArgumentError: bad argument (expected URI object or URI string) error because it will try to make a URI object out of nil.
If you have any calls to delete on a resource (I experienced it in a unit test), you now need to include a referrer in the headers of that call, e.g.:
Didn't see this documented anywhere, and just wanted to raise this for visibility in case anyone is upgrading from
0.9.x
to0.10.x
and is running into this error.There was some logic added to the
destroy
method in the0.10.0
release that uses the referrer on the request to add a turbo stream response when a resource is deleted. If you don't include a referrer on the request, you'll get theArgumentError: bad argument (expected URI object or URI string)
error because it will try to make aURI
object out ofnil
.If you have any calls to
delete
on a resource (I experienced it in a unit test), you now need to include a referrer in the headers of that call, e.g.:The text was updated successfully, but these errors were encountered: