Style Guide

📏 Style Guide

Consistency is key to a maintainable codebase. All eOzka projects follow these core principles.

📝 Commit Messages

We follow the Conventional Commits specification.

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• test: Adding missing tests or correcting existing tests

🎨 Code Linting

• JavaScript/TypeScript: We use our standardized eOzka-Lint-Config (ESLint + Prettier).
• Flutter/Dart: We adhere to the official flutter_lints package with our ZenithTheme stricter overrides.
• Python: We strictly enforce Black formatting and flake8 compliance.

Before submitting any PR, ensure you have run the linting scripts in the respective repository.