Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature Request] Add or improve history actions
See original GitHub issueThanks for the great lib!
It would be nice to have a shortcut to modify Turbo.navigator.history. I find it an essential action since the Back button is not doing what is expected when the browser history is modified without touching Turbo.navigator.history. As a workaround, the invoke action can be used at the moment.
More on the issue: https://discuss.hotwired.dev/t/back-button-not-working/3012
P.S. I’d really love to help but I’m not very familiar with Typescript yet 😕
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, I thought it could be similar to how
redirect_toworks.https://github.com/marcoroth/turbo_power/blob/623a6f5b11608073ac36880bd1f0cc4745a52e56/src/actions/browser.ts#L17-L29 By default it uses the one on
Turbo, but if you don’t want that or if Turbo is not available it falls back towindowSounds OK if that would let one push state solely on
window.historyor theTurbo.navigator.history(sometime you want or another)