Fallback to client side SOR
Open
Nobody has claimed this yet.
p1
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
hi justin, this was a note on the Routing project board. Since we don't have a standup for that any more I made it an issue and will track in web app project
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
The issue mentions the Routing project board and the web app project, but names no files, tests, or entry points. Start by locating the routing and client-side SOR work in the interface repository and clarify the expected fallback behavior; the issue is done only when that behavior and its validation are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100