see https://github.com/foodcoops/foodsoft/pull/907 for reference
and original work by viehlieb
Co-authored-by: viehlieb <pf@pragma-shift.net>
fix PDF Pdf
make explicit deposit in invoices work
add ordergroupname to invoice file name
mark bold sum for vat exempt foodcoops
download multiple group order invoice as zip
chore: fix api test conventions
chore: rubocop -A spec/
chore: more rubocop -A
fix failing test
rubocop fixes
removes helper methods that are in my opinion dead code
more rubocop fixes
rubocop -a --auto-gen-config
* Replace apivore api tests with rswag
* move to OpenAPI Spec 3.0.1
* a swagger UI is now reachable at http://localhost:3000/api-docs/index.html
* swagger file is generated by running `RAILS_ENV=test rails rswag`
and it was moved from /docs/swagger.v1.yml to /swagger/v1/swagger.yml
---------
Co-authored-by: viehlieb <pf@pragma-shift.net>
When the charge_members_manually option is active there is no need for an
explicit balancing step. This new function allows to close_direct all
orders which have an assigned invoice, which is usually indication enough
to find orders which can be closed finally.
This change introduces two new data types to group the financial
transactions. Now every transaction has a "type", which itself belongs
to a "class".
Types should be used add structured information to an transaction, instead
of writing it into the notice textfield. E.g. this could be used to have
different types depending on the source of money (cash vs. bank transfer).
Classes are shown as different columns in the tables and will be uses to
group transactions of specific types. They should be used if not the whole
amount of ordergroup should be used to order food. E.g. if there is a
deposit or membership fee, which is independent of the normal credit.
This will allow us to implement additional features based on classes in
the future. E.g. the sum of transactions in the "membership fee" class
must be positive to allow food orders or show a big warning if it is bellow
a certain value.
