Suggestiongs for next major release breaking changes
Open
Nobody has claimed this yet.
Feature Request
- Dominant language
- JavaScript
- Stars
- 31.3k
- Forks
- 4.8k
- PR merge metrics
- No merged PRs in 30d
Description
- Don't flip
width/heightifformatparameter does not fit dimensions. The orientation parameter only makes sense if a fixed page format like "a4" is provided. (e.g. #3066). - Make some hotfixes the default behavior.
- Maybe make
ptthe default unit (scale factor 1). - Get rid of
floatPrecisionoption in favor ofprecision. - Redesign
getFontListAPI with separate font style and font weight - Get rid of synchronous XHRs and make the respective APIs return a Promise.
- Clean up
htmlAPI. Make it return a proper Promise. - Maybe deprecate or remove
setTextColor- it's the same assetFillColor set/getFontSizeshould use current document unit, not alwayspt. Same for similar functions likegetLineHeight.
Contributor guide
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
Review the proposed breaking changes in this issue and identify the affected APIs, including orientation, units, precision, font handling, synchronous XHR, html, colors, and font sizing. Start by tracing each API to its implementation and existing tests; done means the release scope and migration behavior are agreed for every listed change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100