Lots of 404s in Reference API pages
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 893
- Forks
- 114
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 3
Description
Describe the bug
It's not about Tankstack Store itself, almost all pages of the References API result in a 404.
At least all these pages:
- https://tanstack.com/store/latest/docs/reference/functions/createstore
- https://tanstack.com/store/latest/docs/reference/functions/createatom
- https://tanstack.com/store/latest/docs/reference/functions/createasyncatom
- https://tanstack.com/store/latest/docs/reference/type-aliases/selection
- https://tanstack.com/store/latest/docs/reference/type-aliases/observer
- https://tanstack.com/store/latest/docs/reference/type-aliases/anyatom
- https://tanstack.com/store/latest/docs/reference/interfaces/subscription
- https://tanstack.com/store/latest/docs/reference/interfaces/subscribable
- https://tanstack.com/store/latest/docs/reference/interfaces/readonlyatom
- https://tanstack.com/store/latest/docs/reference/interfaces/readable
- https://tanstack.com/store/latest/docs/reference/interfaces/interopsubscribable
- https://tanstack.com/store/latest/docs/reference/interfaces/internalreadonlyatom
- https://tanstack.com/store/latest/docs/reference/interfaces/internalbaseatom
- https://tanstack.com/store/latest/docs/reference/interfaces/baseatom
- https://tanstack.com/store/latest/docs/reference/interfaces/atomoptions
- https://tanstack.com/store/latest/docs/reference/interfaces/atom
Steps to Reproduce the Bug or Issue
open links above
Expected behavior
should ne be 404s
Screenshots or Videos
Platform
- OS: Mac OS
- Browser: Vivaldi
- Version: NA
Additional context
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 opening the listed Reference API URLs and inspecting how the Store documentation generates routes for functions, type aliases, and interfaces. Trace the relevant documentation entry points, then verify that all listed pages resolve instead of returning 404s.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100