Custom history
See original GitHub issueWould it be possible to allow a custom history object to be passed as a prop to SearchkitManager
? I think this would be useful allow integration with things like react-router-redux.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
The history of customs from the beginning to the present
Customs already existed in the third millennium before Christ in the ancient advanced civilizations of ancient Egypt and the Orient.
Read more >History of the U.S. Customs Service
Only a few days after Customs drew its first breath, on August 5, 1789, the power of the service went from legal theory...
Read more >A Brief History of Customs | Border Bee
Evidence of Customs activity has been excavated all over the world, from the ports of Ancient Greece to the Great Wall of China....
Read more >History - National U.S. Customs Museum Foundation
The US Customs Service was created to provide revenue to the new nation through the collection of duties and tariffs on imported goods....
Read more >Customs - Wikipedia
Customs is an authority or agency in a country responsible for collecting tariffs and for controlling the flow of goods, including animals, transports, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yep @abousamra we upgraded and added hook to provide own history in v2.1
Thanks, I will close this issue down now
Allowing custom history object is not simple, a lot of scenarios need to be considered.
Suppose we have page A, B(Searchkit), C. They are in a single page app.
PUSH
. Only when a history’s first generated location or browser’spopstate
event generated location has aPOP
state.PUSH
orPOP
(use browser’s forward button). If it’s aPOP
, then the listener is triggered a new search is done, which shouldn’t happen.To solve above issues, I propose that search is triggered and only triggered by history’s event and providing a
pauseListenHistory
andresumeListenHistory
to disable the listener if on other pages.