JoeZ99

currently, the response is a simple 200 OK status response. with no info whatsoever of what just happened. it could carry info about how many items were reindexed, the size,...

deprecated warning with capybara 2.7.0

2

this is the message `DEPRECATED: Passing a block to Capybara::server is deprecated, please use Capybara::register_server instead` because of this code in capybara-puma ``` ruby Capybara.server do |app, port| Puma::Server.new(app).tap do...

I'm afraid I'm pushing it too hard, but here it goes ... Just a few test for the feature added a few days ago ...

tests for - Invoice - Estimate - RecurringInvoice @gissues:{"order":75,"status":"notstarted"}

from the docs: # ``` public DatePeriod::__construct ( DateTime $start , DateInterval $interval , int $recurrences [, int $options ] ) public DatePeriod::__construct ( DateTime $start , DateInterval $interval ,...

build base models custom methods: Common, Invoice, Recurring and Estimate

1

Give to the following entities: - Invoice - Recurring - Common The custom methods they have in previous siwapp. Also make the tests. @gissues:{"order":98.80952380952381,"status":"backlog"}

If a recurring invoice has this option checked, when it generates an invoice, the invoice is automatically sent. @gissues:{"order":83.33333333333333,"status":"backlog"}

fixtures for properties, tags, series

1

@gissues:{"order":50,"status":"notstarted"}

separate between init options and regular options

1

so a potential `max_restarts` option is useful fix #15

Because it is set to be used as a `DynamicSupervisor` regular option, but as stated in https://github.com/elixir-lang/elixir/issues/13675, the `max_restarts` option only works as an init option