c6e1658ffe
* Refactor company properties to be presented from settings object instead of company properties * Working on Email Tests * Working on emails * Working on email templats * Include text version of email * Refactor Email template builder into trait' * Fix for custom_value4 * Refactor payment_date -> date && payment_type_id -> type_id * expose paymentables to API * expose paymentables to API * Implement a next_send_date field in invoice/quote tables to allow control over reminder scheduling * Add custom_values to users,documents and company_gateways tables
Invoice Ninja version 2.0 is coming!
We will be using the lessons learnt in Invoice Ninja 4.0 to build a bigger better platform to work from. If you would like to contribute to the project we will gladly accept contributions for code, user guides, bug tracking and feedback! Please consider the following guidelines prior to submitting a pull request:
Quick Start
Currently the client portal and API are of alpha quality, to get started:
git clone https://github.com/invoiceninja/invoiceninja.git
git checkout v2
cp .env.example .env
cp .env.dusk.example .env.dusk.local
composer update
npm i
npm run production
php artisan migrate:fresh --seed && php artisan db:seed --class=RandomDataSeeder
Navigate to
http://ninja.test:8000/client/login
user: user@example.com
pass: password
Contribution guide.
Code Style to follow PSR-2 standards.
All methods names to be in CamelCase
All variables names to be in snake_case
Where practical code should be strongly typed, ie your methods must return a type ie
public function doThis() : void
PHP >= 7.3 allows the return type Nullable so there should be no circumstance a type cannot be return by using the following:
public function doThat() ?:string
To improve chances of PRs being merged please include tests to ensure your code works well and integrates with the rest of the project.
Documentation
API documentation is hosted using Swagger and can be found HERE
Current work in progress
Invoice Ninja is currently being written in a combination of Laravel for the API and Client Portal and Flutter for the front end management console. This will allow an immersive and consistent experience across any device: mobile, tablet or desktop.
To manage our workflow we will be creating separate branches for the client (Flutter) and server (Laravel API / Client Portal) and merge these into a release branch for deployments.