Skip to content

openpdf-html - reformating according to defined checkstyle rules#1530

Open
stomaszek wants to merge 21 commits intoLibrePDF:masterfrom
stomaszek:feature/checkstyle-openpdf-html
Open

openpdf-html - reformating according to defined checkstyle rules#1530
stomaszek wants to merge 21 commits intoLibrePDF:masterfrom
stomaszek:feature/checkstyle-openpdf-html

Conversation

@stomaszek
Copy link
Copy Markdown

@stomaszek stomaszek commented Apr 14, 2026

Description of the new Feature/Bugfix

openpdf-html module reformatted according to defined checkstyle rules

Related Issue: #

none

Unit-Tests for the new Feature/Bugfix

none

Compatibilities Issues

no - just reformating

Your real name

Sławomir Tomaszek

Testing details

no additional testing - just core reformat

@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Apr 14, 2026

Not up to standards ⛔

🔴 Issues 3 high · 11 medium · 8 minor

Alerts:
⚠ 22 issues (≤ 0 issues of at least minor severity)

Results:
22 new issues

Category Results
BestPractice 3 medium
1 minor
ErrorProne 7 medium
3 high
CodeStyle 7 minor
Complexity 1 medium

View in Codacy

🟢 Metrics 0 complexity · 1 duplication

Metric Results
Complexity 0
Duplication 1

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes. Give us feedback

@wang0331
Copy link
Copy Markdown
Contributor

1、What is the purpose of this PR? Why is the refactoring needed?

2、How is the testing going after the refactoring?

@sonarqubecloud
Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
4.7% Duplication on New Code (required ≤ 3%)
D Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@stomaszek stomaszek marked this pull request as ready for review April 22, 2026 21:12
@stomaszek
Copy link
Copy Markdown
Author

1、What is the purpose of this PR? Why is the refactoring needed?

Unification layout of code across all modules according to defined code style and checstyle rules.

2、How is the testing going after the refactoring?

It is just reformatting without functionality changed - I'm not thinking about additional verification except defined in build process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants