Skip to content

Write a contributing guidelines file #13

Description

@tlein

Formatting

  • 4 spaces as tab
  • TypeScript type colons hug the identifier, not the type
  • Open curly brackets are on the same line
  • Must always use curly brackets around if/while/for/etc...
  • All private members (variables, functions, get/set) must begin with an underscore (_)
  • Variables and functions are camelCase
  • const variable names are SCREAMING_CASE
  • Must pass all linter formatting checks

Writing Issues

  • Describe what is the problem
  • Provide a relevant sample code demonstrating the problem if necessary

Opening Pull Requests

  • Unit test all new functionality
  • E2E test when appropriate
  • Follow PR description format as they are used as the squash commit for the PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions