Stéphane Brossier
Stéphane Brossier
* In https://github.com/killbill/killbill/commit/85a045f5a14b7112dc8a615414bd5cb8f52ecef8, there is a new test case that shows the current behavior. * In https://github.com/killbill/killbill/commit/415c0c0a050ccf372989563688fe2c04d8fd8593, there is a prototype fix that removes the pro-ration when transition to a...
Catalog has a Fixed Item type but we really need two of them: - One is for setup which is non repairable and non pro-ratable - One would be fixed...
Today, our `FIXED` items are being invoiced whenever a new `Plan` containing such `FIXED` item is active. We had some requests to make this behavior configurable and possibly disable any...
See [conversation](https://groups.google.com/g/killbilling-users/c/RawQAn7zv-A) for reference. In a nutshell, since CTD reflects how far ahead we have invoiced, voiding an invoice should reset accordingly such CTD.
Our code base was started prior Java fluent api, and so we embraced Guava (e.g `Iterables.xxx`) to perform filtering, sorting, merging operations on data structures - e.g [here](https://github.com/killbill/killbill/blob/killbill-0.22.28/profiles/killbill/src/test/java/org/killbill/billing/jaxrs/TestUsage.java#L85) We would...
For the payment control plugin api, we allow plugins to modify plugin properties passed in the `priorCall`, in such a way that next plugins in the list would see the...
When triggering an invoice run -- dry-run or not -- allow the caller to specify plugin properties that would be passed to the plugin.
The goal is to provide a mechanism to group certain subscriptions on their own invoices. More specifically, the feature would allow to have all items tied to a certain group...
Today, when an invoice needs to be paid, the payment code extracts the default payment method associated with the account. An invoice contains potentially several items, each of which can...
Extracted from [this comment](https://github.com/killbill/killbill/pull/1673#issue-1218122393), there are some remaining questions with regards to ordering our subscription events: * Should the sorting logic be stricter at ordering ties for variuous types such...