Dwayne Charrington
Dwayne Charrington
I remember raising this about a year ago and I could have sworn that we had this already. Is that not the case currently @bigopon ?
@bigopon Are we still wanting this PR?
Closing this as a fix appears to have been merged.
I am going to close this issue as the consensus appears to be compose is for the internal of a component.
@jwx Are there any plans to support getting the existing route on the previous property?
I guess I was just looking for a less convoluted solution. A property that gives you the previously loaded instruction without having to go and find it yourself. I'm just...
The previous route can be found `instruction.previous.route.match` it's a bit wordy, but it works. I think initially, I might have been looking for a simple one-liner to access the previous...
Thank you for this. I can confirm we are seeing the same behaviour and a fix for this should be out soon.
@bigopon Is this still an area of concern that we want to document or a code solution using the proposed `@primary` decorator?
@bigopon Are we still of the opinion that this PR deviates from how we want this behaviour to work? If so, it should be closed.