liveview-native / liveview-native/liveview-client-swiftui
Better error when a native view is not available
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 440
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
When people are generating a project and don't add ReconnectingView, etc.. they are running into an error because SwiftUI tries to access a view that doesn't exist. I think we should do one of the two:
1. don't error if we can avoid it
2. provide a better error message to tell people what to do
Contributor guide
No contributing guide indexed for this repository
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 reproducing project generation without ReconnectingView or another native view, then trace the SwiftUI path that tries to access the missing view. Decide whether the missing view can be skipped or needs an actionable error message. Done means generation no longer fails unexpectedly and, if it still cannot proceed, clearly tells users what to add or change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100