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
Jumped from v0.8.1, so I realize this might have been a known/intentional breaking change, but I'm seeing unexpected behavior on an index route. Also v possible this is just user-error/not accounting for a change, so please steer me toward docs if I've missed something obvious. Getting the following error on a route that used to work:
"Error: Ziggy error: object passed as 'filter' parameter is missing route model binding key 'undefined'."
On Ziggy v0.8.1, this did what we expected for an index route—we pass any applied filters via a nested filter object which were then "converted" to query parameters (eg, /people?filter[name]=Dwyer). This bit of functionality leans on Spatie's Query Builder, in case that's helpful context. Now we're getting the error above.
TIA for any suggestions/thoughts you all might have!
Ziggy version
v1.3.5
Laravel version
v8.53.1
Description
Jumped from v0.8.1, so I realize this might have been a known/intentional breaking change, but I'm seeing unexpected behavior on an
index
route. Also v possible this is just user-error/not accounting for a change, so please steer me toward docs if I've missed something obvious. Getting the following error on a route that used to work:"Error: Ziggy error: object passed as 'filter' parameter is missing route model binding key 'undefined'."
On Ziggy v0.8.1, this did what we expected for an
index
route—we pass any applied filters via a nestedfilter
object which were then "converted" to query parameters (eg,/people?filter[name]=Dwyer
). This bit of functionality leans on Spatie's Query Builder, in case that's helpful context. Now we're getting the error above.TIA for any suggestions/thoughts you all might have!
Ziggy call and context
Ziggy configuration
Route definition
The text was updated successfully, but these errors were encountered: