liveview-native / liveview-native/liveview-native-swiftui-deviceactivity
Modifier -> DeviceActivity -> DeviceActivityReport -> View Implementations: accessibilityRotor(_:textRanges:)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Doc: https://developer.apple.com/documentation/deviceactivity/deviceactivityreport/accessibilityrotor(_:textranges:)-14wjn
https://developer.apple.com/documentation/deviceactivity/deviceactivityreport/accessibilityrotor(_:textranges:)-4cf5m
https://developer.apple.com/documentation/deviceactivity/deviceactivityreport/accessibilityrotor(_:textranges:)-7mzzz
https://developer.apple.com/documentation/deviceactivity/deviceactivityreport/accessibilityrotor(_:textranges:)-9knb
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 with the Apple Developer documentation links for DeviceActivityReport.accessibilityRotor(_:textRanges:), then locate the corresponding View implementation in this repository. Done means the documented modifier overloads are implemented and validated against the referenced API behavior; no test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100