This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-03
Channels
- # aws (6)
- # babashka (77)
- # beginners (102)
- # clj-kondo (24)
- # cljsrn (17)
- # clojure (40)
- # clojure-australia (15)
- # clojure-europe (50)
- # clojure-nl (4)
- # clojure-uk (4)
- # clojurescript (9)
- # conjure (2)
- # cursive (28)
- # data-science (1)
- # datomic (21)
- # events (5)
- # joker (15)
- # malli (136)
- # meander (1)
- # off-topic (25)
- # pathom (4)
- # podcasts-discuss (2)
- # portal (12)
- # portkey (1)
- # powderkeg (1)
- # practicalli (5)
- # re-frame (14)
- # reitit (3)
- # shadow-cljs (49)
- # specter (4)
- # tools-deps (4)
- # unrepl (1)
Is there a current best practice for what to do with browser history if a user deep-links to a page?
This is in the context of Reitit's frontend browser history integration.
For example, suppose I had a todo app, where the first page in the normal workflow is a list of todo items, and the
user would normally click on one of those to route to a second page to edit the todo item.
What if the user skips the first page by deep-linking to a specific note?
Is it better to:
a) Recognize that deep-linking occured and then reconstruct the browser history based on what it would have been had they gone through the normal workflow?
or
b) Ignore the browser history and just push-state
for all navigation events?