Skip to content

refactor: normalize code style and formatting across repo#1114

Closed
remivanboxem wants to merge 1 commit intoINGInious:mainfrom
remivanboxem:formatting
Closed

refactor: normalize code style and formatting across repo#1114
remivanboxem wants to merge 1 commit intoINGInious:mainfrom
remivanboxem:formatting

Conversation

@remivanboxem
Copy link
Copy Markdown
Contributor

  • Added Ruff dependency and rules inside pyproject.toml
  • Format the entire project using ruff --config pyproject.toml format inginious/ command.

This change allows having a clearer codebase and should not add regression. To enforce this stylistic change, maintainers can either:

  • refuse any PRs or commits that doesn't respect this style
  • add a GitHub action workflow that will automatically reformat any incoming PR.

- Added `Ruff` dependency and rules inside `pyproject.toml`
- Format the entire project using `ruff --config pyproject.toml format
  inginious/` command.

This change will allow to have a clearer codebase and should not add
regression.
@codacy-production
Copy link
Copy Markdown

Not up to standards ⛔

🔴 Issues 1 critical · 58 high · 37 medium

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

Results:
96 new issues

Category Results
ErrorProne 2 high
Security 56 high
1 critical
1 medium
Complexity 36 medium

View in Codacy

🟢 Metrics 7 complexity · 6 duplication

Metric Results
Complexity 7
Duplication 6

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.

@anthonygego
Copy link
Copy Markdown
Member

The changes proposed sometimes seem way less readable than the previous lines due to an abusive use of new lines. Is this really the recommended standard ?

In any case I'm not sure we would need to update the entire codebase once because it would break any work made above: our work, but also community work that we want to respect even if those changes don't come back to upstream.

I think this is something we could simply set for future PRs. Time would do the necessary and replace the old code. However I'd like another thought on this (@nrybowski) because I dont really facny having a lot of new lines everywhere.

@anthonygego anthonygego closed this May 8, 2026
@remivanboxem remivanboxem deleted the formatting branch May 8, 2026 08:16
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