-
Notifications
You must be signed in to change notification settings - Fork 4
Coding Standards
This page outlines the core coding standards used across all practicum projects.
These standards ensure consistency, readability, and professionalism in student code β regardless of programming language or IDE.
Each section provides clear guidelines, examples, and tools that help you write clean, maintainable code.
Use the links below to navigate to specific subpages.
Below are the available coding standards for each supported language.
Each link includes detailed conventions, examples, and best practices.
Covers ES module syntax, variable naming, async/await rules, TypeScript typing guidelines, React/Expo conventions, and more.
Includes PEP 8 conventions, docstrings, indentation rules, environment best practices, and module organization.
Focuses on query structure, uppercase keywords, indentation, JOIN formatting, and view/procedure standards.
Optional page for any language used in specialty tracks or projects.
Proper linting and formatting helps ensure code consistency across the team.
These rules are enforced in most projects and must be followed before submitting a pull request.
Explains the shared Prettier config, formatting standards, and how to auto-format code on save.
Documents required ESLint rules, common error types, and how to resolve them.
Walks students through configuring their IDE to automatically format code on save (VS Code, WebStorm, Android Studio).
Names must be readable, predictable, and consistent across all repos. This page outlines rules for casing, file structure, and naming conventions.
If you are unsure which standards apply to your project, ask your instructor or refer to the projectβs README.
Home β’ New Student Onboarding β’ Guides β’ Projects β’ Code of Conduct β’ FAQ
Last updated: 12/7/2025