Cornell AppDev Bible
  • Introduction
  • Standards
    • Git
      • Git Issues
      • Advanced Git
    • iOS
      • Xcode
      • Language
      • Style
      • SwiftLint
      • Architecture
      • Libraries
        • IGListKit
      • Layout
      • Networking
      • State
      • Persistence
      • Table Views
      • Making a Pull Request
      • Reviewing a Pull Request
      • Secret Keys
      • Continuous Integration
    • Android
      • Language
      • Storing Secret Keys
      • Pull Request Reviews
    • Backend
      • Continuous Integration
      • Pull Request Reviews
      • Style + Linting
    • Web
      • Servers
      • JavaScript
      • Python
  • API Specifications
    • Uplift
    • Pollo
    • Eatery
Powered by GitBook
On this page
  1. Standards
  2. Backend

Style + Linting

Information related to Style + Linting.

Unlike iOS, Backend doesn't have an editor that's obviously superior to others. Popular choices by previous members include: Atom, VSCode, vim, emacs.

However, it's important that your editor of choice includes linting.

What is linting?

When your editor lints your code, it outputs errors and warnings regarding code that is stylistically incorrect. Generally, this relates to syntactic errors but can include warnings/errors related to the code itself: for example, a linter might output warnings that a variable was defined but never used.

This allows us to automate this step while writing code, and helping us find stylistic/logical errors resulting from typos and other mistakes much more easily!

PreviousPull Request ReviewsNextWeb

Last updated 6 years ago