linebender / linebender/parley
Enable 3rd-party builders
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 736
- Forks
- 120
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 53
Description
We would like to move Parley to a design where the "builders" (such as `RangedBuilder` and `TreeBuilder`) are external, built on top of a core API that is agnostic to the high-level representation (the core will likely represent styles as a set of *non-overlapping* ranges).
In order to do this we need to expose more of the low-level parts of Parley such as `LayoutContext` and possibly `ResolveContext`, `BidiResolver` and `ShapeContext`.
Making changes such that the existing builders depend only on public APIs is likely to a good way to start.
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 existing RangedBuilder and TreeBuilder implementations, then trace their use of LayoutContext, ResolveContext, BidiResolver, and ShapeContext. Identify which low-level APIs they require and determine how those APIs can support external builders. Done means the existing builders depend only on public APIs and the core remains agnostic to high-level representation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100