When using relocate() during an integration test, the original action is still called.
That interesting. here’s the previous conversation I was remembering from 2017.
Luis says the code after will run... probably only on early returns
That was Gavin quoting what you had told him back then.
Meh, I just realized that link is to a DM with Gavin, so I suppose the link isn’t useful for anyone outside of Gavin and myself Either way, that was the conversation I was referring to in which I thought it was said that the current behavior was working as designed by Luis I didn’t look at the code at the time but I see there has been a throw in there for a very long time. So I guess the question now is why it isn’t working.
What's the next step on this?
I would assume to figure out why the current implementation doesn’t work.
Had a Mentoring call, and this bug is still holding them up.
Their app uses relocation's all over the place, and it’s blocking them.
I’ll try and create a test case.