QuestPDF / QuestPDF/QuestPDF

Configurable default unit

Open
#1,092 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
14.2k
Forks
771
Avg merge
3h 37m
Merged PRs (30d)
11

Description

At the moment the default unit is points for every method, but in our project we use millimeters. So for every method call we have to overrule the default which feels redundant.

It would be great to be able to set the default unit in the settings at the start of the application and that every method uses that default unit unless the optional unit parameter is set in the method calls.

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 by locating the application settings entry point and the methods that accept an optional unit parameter. Trace where points is selected as the current default across the fluent API, then determine how a configurable default can apply consistently while explicit unit arguments still override it. Done means the setting works for every relevant method and explicit units retain their behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.