This message was deleted.

if you use auto naming, you rarely run into this. if you don't use autonaming, you'll need to set the

deleteBeforeReplace

resource option

yeah the problem is the

routeKey

clash. I use auto-naming for the resource but this is an exceptional case where the basename changes and the provider doesn't know that the old resource being deleted is related at all to the new one created (with the same

routeKey

which therefore fails).

I wouldn’t mind seeing a bit of code if you’re still experiencing this, specifically what your

Route

declarations look like. If you are using auto-naming for the

Route

resource, then there shouldn’t be a conflict, as the

routeKey

should just be updated, rather than result in a whole new

Route

. That doesn’t seem to be what you’re seeing, though, so would be good to see some code if you could share any.