Different behavior of Source::all_families
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 840
- Forks
- 137
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 1
Description
Fontconfig's Source checks that families list isn't empty, but other implementations aren't. I think this should be unified. But not sure in what way.
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 at src/sources/fontconfig.rs around line 65, where Source checks that the families list is not empty, then compare the other Source implementations. Decide how all_families should behave consistently when the family list is empty; the issue is done when the implementations follow one agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100