Development Guidelines - Luther Systems

This page lists the recommended guidelines for developers building applications on the Luther platform

Dates should be represented as YYYY-MM-DD
Money should be represented as decimal-string and use the decimal library
Calculations in the Oracle with large numbers should use maths.Big
Use the svcerr package to return proper error codes in the Oracle
Follow the testing guidelines
The whole stack should run locally on your laptop at all times
Run all tests for every PR against the master branch
Run end-to-end Martin tests upon every successful deployment to integration
Avoid making breaking (backwards incompatible) data model changes
Use lutherauth for user authentication only, and enforce authorisation at application layer

6.3.2. Development Guidelines