[Feature Request] Debug Logs
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 822
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
I'd love to have a debug option that allows printing all artboard names (and subartboards), assets names, inputs, text runs and their paths, etc.
It's not always obvious what is available or if the riv file is configured correctly. Printing them in code will help ensure the right paths and options are used and help with debugging any issues with layers that may not be exported correctly.
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
No files, tests, or entry points are named in the issue. Start by locating the Swift runtime areas that expose artboards, subartboards, assets, inputs, text runs, and their paths. Done means a debug option prints those requested items so users can inspect Rive file configuration and exported layers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100