feat: add universal formatting configuration (black, prettier, editorconfig) #71

fenopy · 2026-06-24T11:46:46Z

fenopy commented

2026-06-24 11:46:46 +00:00

Notes

@viewit, please feel free to customize to your preferences. I was just looking to add some consistency between developers and editors.
All files require a first-time format

pip install -r requirements-dev.txt # Install black
npm install # Install prettier

black . # Format Python
npm run format:web # Format JavaScript/web files

Description

Adds universal code formatting configuration for Python and JavaScript/web files to maintain consistent code style across the project without requiring extensive tooling.

Includes:

.editorconfig - baseline formatting rules respected by all editors
requirements-dev.txt - Black for Python formatting
package.json - Prettier for JavaScript/JSON/HTML/CSS formatting

Developers can format locally with black . and npm run format:web before commits.

Closes # (if applicable)

Type

Bug fix
Feature
Documentation
Refactoring

Tested with

OrcaSlicer Version: N/A
Printer: N/A
Moonraker/Klipper Version: N/A

Checklist

No tests required (configuration files)
CHANGELOG.md updated (optional - dev-only dependency)
No debug code included

## Notes @viewit, please feel free to customize to your preferences. I was just looking to add some consistency between developers and editors. All files require a first-time format `pip install -r requirements-dev.txt # Install black` `npm install # Install prettier` `black . # Format Python` `npm run format:web # Format JavaScript/web files` ## Description Adds universal code formatting configuration for Python and JavaScript/web files to maintain consistent code style across the project without requiring extensive tooling. Includes: - `.editorconfig` - baseline formatting rules respected by all editors - `requirements-dev.txt` - Black for Python formatting - `package.json` - Prettier for JavaScript/JSON/HTML/CSS formatting Developers can format locally with `black .` and `npm run format:web` before commits. ## Related Issue Closes # (if applicable) ## Type - [ ] Bug fix - [x] Feature - [ ] Documentation - [ ] Refactoring ## Tested with - OrcaSlicer Version: N/A - Printer: N/A - Moonraker/Klipper Version: N/A ## Checklist - [x] No tests required (configuration files) - [ ] CHANGELOG.md updated (optional - dev-only dependency) - [x] No debug code included

fenopy added 1 commit 2026-06-24 21:23:55 +00:00

fix: pull_request_template.md ins Root-Verzeichnis (Gitea-Anforderung)

Nightly Build / build (push) Has been cancelled

PR Check / lint-and-test (pull_request) Failing after 5s

216b2de2c0

viewit manually merged commit 216b2de2c0 into nightly

2026-06-24 21:23:57 +00:00

fenopy deleted branch feat/formatting

2026-06-24 21:25:34 +00:00

viewit commented

2026-06-28 17:22:56 +00:00

Thanks for the PR @fenopy! The idea is appreciated — consistent formatting is always a good thing.

For now I am holding off on merging this. The main concern is that a first-time format pass would touch nearly every file in the repo, making diffs and git blame much harder to read. For a project with occasional contributors this tradeoff does not feel worth it yet.

If the contributor base grows I will revisit this. Feel free to use black/prettier locally in your own workflow in the meantime!

Thanks for the PR @fenopy! The idea is appreciated — consistent formatting is always a good thing. For now I am holding off on merging this. The main concern is that a first-time format pass would touch nearly every file in the repo, making diffs and git blame much harder to read. For a project with occasional contributors this tradeoff does not feel worth it yet. If the contributor base grows I will revisit this. Feel free to use black/prettier locally in your own workflow in the meantime!

👍 1

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#71

Allow edits from maintainers