[GH-ISSUE #23] Create a style guide and editorconfig file #10

New issue

Closed

opened 2026-02-27 15:45:57 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 15:45:57 +03:00

Owner

Originally created by @jhollowe on GitHub (May 20, 2020).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/23

Create a standard for how the code should be formatted. This includes at least a basic style guide for things that can't be linted and fixed, as well as an editorconfig file for everyone to follow and possibly set up an automatic linter.

Originally created by @jhollowe on GitHub (May 20, 2020). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/23 Create a standard for how the code should be formatted. This includes at least a basic style guide for things that can't be linted and fixed, as well as an [editorconfig](https://editorconfig.org) file for everyone to follow and possibly set up an automatic linter.

kerem

2026-02-27 15:45:57 +03:00

closed this issue
added the
type:meta

type:maintenance 🛠️
labels

kerem commented

2026-02-27 15:45:58 +03:00

Author

Owner

@jhollowe commented on GitHub (Feb 24, 2022):

Style standards enforced by pre-commit hooks (black, isort, flake8, etc) and editorconfig not really needed.

@jhollowe commented on GitHub (Feb 24, 2022): Style standards enforced by pre-commit hooks (black, isort, flake8, etc) and editorconfig not really needed.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmoxer#10

No description provided.

Rows
Columns