Skip to content

chore: add .editorconfig with formatting rules#329

Open
feng83232 wants to merge 1 commit into
lobster-trap:mainfrom
feng83232:editorconfig
Open

chore: add .editorconfig with formatting rules#329
feng83232 wants to merge 1 commit into
lobster-trap:mainfrom
feng83232:editorconfig

Conversation

@feng83232

Copy link
Copy Markdown

Closes #10

Adds an .editorconfig file to enforce consistent coding styles across editors:

  • charset, end_of_line, indentation for all file types
  • Language-specific rules for Python, Rust, TS/JS, C/C++, Go, Lua, etc.
  • trailing whitespace trimming and final newline enforcement

@lobster-trap

Copy link
Copy Markdown
Owner

Diagnostics are still blocking review on this PR.

Please rebase onto the current upstream branch and run the repository build script so the script-generated diagnostic bundle is committed to this PR:

git fetch upstream
git rebase upstream/main
python3 build.py
git push --force-with-lease

Please do not manually create, copy, or edit diagnostic files. python3 build.py automatically generates and commits the fresh encrypted diagnostic artifacts.

A valid PR must include a matching diagnostic/build-*.json and diagnostic/build-*.logd pair in the PR's changed files. The JSON should be generated by build.py, and the .logd file should be the encrypted diagnostic archive generated by the same run.

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.

[$20 BOUNTY] [Config] Add .editorconfig with consistent project formatting rules

2 participants