Component handling: add API for checked insertion and removal?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 61
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I had the idea of having `Layer` and `Glyph` cooperate to check that inserting, modifying and removing components ensures that we never end up with dangling components. [glifparser has code for handling](https://github.com/linebender/norad/issues/107#issuecomment-997388325). Need to investigate:
1. Does it add value?
2. Should it be used for UFO loading or just for the programmatic API? When loading UFOs, how to handle glyphs that exist but aren't added yet?
3. Are there situations where you'd need an unchecked way of messing with components?
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 reviewing the Layer and Glyph component-handling entry points and the linked glifparser discussion. Investigate whether checked insertion, modification, and removal add value, how they interact with UFO loading, and whether an unchecked API is needed. Done means the API scope and loading behavior are decided and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100