Nested page loader indicator
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
I have a page loader indicator on the root layout level.
But I also have a page loader indicator on deeper layouts.
The problem is that knowing when to show the correct page loader without Sveltekit giving some extra info is impossible.
The navigating store only tells me the from and to URLs.
But that doesn't tell me which layout is going to change.
Or what loader is going to be called?
Describe the proposed solution
Maybe we could have a more local navigating store inside every layout / page?
Or maybe a will-unload indicator that will let me know that a given layout / page is going to be replaced when the navigation is done. I'm also open to other solutions. Or if there are any existing ones.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the navigating store and how nested layouts and pages participate in navigation. Compare the requested local store or will-unload indicator against the current from and to URL information. Done would mean defining and implementing a clear way for each layout or page to know whether it will be replaced, with behavior that supports the appropriate loader indicator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100