mirror of
https://github.com/Frooodle/Stirling-PDF.git
synced 2025-08-11 13:48:37 +02:00
# Description of Changes - **What was changed** - Bumped `java.format.settings.google.version` to **1.28.0** in `.devcontainer/devcontainer.json` and `.vscode/settings.json`. - Expanded ignore patterns in `.devcontainer/devcontainer.json` to cover `app/core/`, `app/common/`, `app/proprietary/` directories. - Added a new top‐level `.dockerignore` to exclude build artifacts, virtual environments, logs, OS files, and markdown docs. - Consolidated EditorConfig YAML globs into `*.{yml,yaml}` to remove duplication. - Fixed missing newline in `.github/config/.files.yaml` and added label metadata (`from_name`/`description`) in `.github/labels.yml`. - Updated `build.gradle`: - Introduced `junitPlatformVersion = "1.12.2"` and replaced hard-coded launcher versions. - Applied the `jacoco` plugin across all subprojects and configured `jacocoTestReport` (XML + HTML). - Wire-up `jacocoTestReport` to run after tests. - **Why the change was made** - Ensure all formatting tools (Google Java Format) stay in sync across editors and containers. - Clean up ignore rules to prevent build artifacts and sensitive files from creeping into images and repos. - Improve CI visibility by generating code-coverage reports with JaCoCo. - Keep GitHub configuration files well-formed and enrich label definitions for automation. --- ## Checklist ### General - [x] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [x] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [x] I have performed a self-review of my own code - [x] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md#6-testing) for more details.
47 lines
973 B
INI
47 lines
973 B
INI
root = true
|
|
|
|
[*]
|
|
charset = utf-8
|
|
indent_style = space
|
|
indent_size = 4
|
|
end_of_line = lf
|
|
max_line_length = 127
|
|
insert_final_newline = true
|
|
trim_trailing_whitespace = true
|
|
|
|
[*.java]
|
|
indent_size = 4
|
|
max_line_length = 100
|
|
|
|
[*.py]
|
|
indent_size = 2
|
|
|
|
[*.gradle]
|
|
indent_size = 4
|
|
|
|
[*.html]
|
|
indent_size = 2
|
|
insert_final_newline = false
|
|
trim_trailing_whitespace = false
|
|
|
|
[*.js]
|
|
indent_size = 2
|
|
|
|
[*.css]
|
|
# CSS files typically use an indent size of 2 spaces for better readability and alignment with community standards.
|
|
indent_size = 2
|
|
|
|
[*.{yml,yaml}]
|
|
# YAML files use an indent size of 2 spaces to maintain consistency with common YAML formatting practices.
|
|
indent_size = 2
|
|
insert_final_newline = false
|
|
trim_trailing_whitespace = false
|
|
|
|
[*.json]
|
|
# JSON files use an indent size of 2 spaces, which is the standard for JSON formatting.
|
|
indent_size = 2
|
|
|
|
[*.jsonc]
|
|
# JSONC (JSON with comments) files also follow the standard JSON formatting with an indent size of 2 spaces.
|
|
indent_size = 2
|