mirror of
https://github.com/Stirling-Tools/Stirling-PDF.git
synced 2025-07-23 13:45:21 +00:00
f01ad11843
# Description of Changes - Added `charset = utf-8` and defined `indent_size = 2` for `*.css`, `*.json`, `*.jsonc`, and `*.yml` in `.editorconfig` to ensure consistent formatting across file types. - Improved labeler rules in `.github/labeler-config-srvaroa.yml` by expanding path coverage for labeling Java and CI-related files. - Upgraded pre-commit hooks: - `ruff` from `v0.11.11` to `v0.12.0` - `gitleaks` from `v8.26.0` to `v8.27.2` - Updated `codespell` args to ignore new terms like `thirdParty`, `tabEl`, `tabEls`. - Enhanced `.vscode/settings.json` and `extensions.json`: - Added formatting rules for `json`, `jsonc`, `markdown`, `python`, and `gradle` files. - Included additional extensions for Markdown and Gradle. - Applied detailed HTML formatting preferences. --- ## 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/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/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/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/DeveloperGuide.md#6-testing) for more details. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
53 lines
1.1 KiB
INI
53 lines
1.1 KiB
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
|
|
|
|
[*.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
|
|
|
|
[*.yml]
|
|
# YML files follow the same conventions as YAML files, using an indent size of 2 spaces.
|
|
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
|