Coding Standards

Artconomy adheres to coding standards. While best practices evolve, some common elements remain. This article is here to catalog the ones we expect to apply continually. This document is not intended to be comprehensive, just to set a floor of expectations.

Automated Quality Tools

Artconomy development projects are expected to use:

1. Formatting, so that code style is consistent
2. Linting, to prevent common errors and promote idiomacy
3. Continuing Integration, so that tests are not missed

Workflow Expectations

All changes to the code base must be in a Merge Request. Commit messages should follow conventional commit standards.

Issues, including bugs, and feature enhancement requests, should be filed in the relevant issues list of the repository. These should be updated and closed once completed.