Handling serialization errors
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 61
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Invoking `Ufo::save` may error out early, but erroring out on the `Glyph::save` level leaves a half-written UFO on disk. How to handle? Also needs a review of structures that may fail validation mid-flight, like fontinfo.
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 tracing the serialization paths from Ufo::save and Glyph::save, then review structures such as fontinfo that may fail validation mid-flight. Determine how partially written UFOs should be prevented or handled, and verify the behavior for serialization and validation failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100