linebender / linebender/tiny-skia

Some convenient APIs don't have pub visibility

Open
#153 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.6k
Forks
99
Avg merge
2h 52m
Merged PRs (30d)
1

Description

There are several APIs that could be made public to improve usability. For example, `PathBuilder::cubic_to_pt` is currently `pub(crate)`, but it's particularly convenient when the control points are the results of complex manipulations, as it allows passing these point values directly. In contrast, `cubic_to` requires destructuring points into individual coordinates, which forces me to create temporary variables.

Is there any specific reason why these APIs cannot be public?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the PathBuilder::cubic_to_pt and cubic_to entry points named in the issue, then inspect related PathBuilder APIs and their visibility. Determine which convenience APIs should be public and why, and check existing coverage for these methods. Done means the agreed APIs are publicly usable with appropriate verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.