Differentiate between going back and navigating to a route

[maximvanhove]

Differentiate between going back and navigating to a route

[tomexx]

It's probably enough to introduce another check using _current and _history.length properties. I can create a PR later.

[MaximVanhove]

The problem is that the package listens on route enter and doesn't know if it went back by a button in the menu, the back button you added or the native back button.

[tomexx]

@MaximVanhove Yes... then that's no use in certain scenarios like I have... :/

[MaximVanhove]

Could you explain your scenarios? Maybe I can help.

[tomexx]

I need to differentiate these two scenarios:

Page A -> navigate to Page B -> navigate to Page A

Page A -> navigate to Page B -> back button (returning to Page A)

[tomexx]

Page A -> navigate to Page B -> navigate to Page A

the third step should be stored as a separate item in history array, then it would work as expected with all the methods I think

[MaximVanhove]

I think you can use the click event on the button and emit an event. What would you like to do if you click the back button?

[tomexx]

Well, that's tricky. I need to watch $route changes and then show or hide some component, depending on if user went back from certain route or came there from another place. Your package would solve this easily without handling events which would add complexity

[MaximVanhove]

I guess you could fork my repo and modify it so that it only writes history. Then use the click event on the button to go back to the last.