Skip to content
#

billing

Here are 254 public repositories matching this topic...

pierre
pierre commented Feb 18, 2020

When we run our invoicing logic, we print the billing events for debugging (see DefaultInternalBillingApi):

DefaultBillingEvent{type=CREATE, effectiveDate=2017-05-11T13:44:31.000Z, planPhaseName=sports-monthly-evergreen, subscriptionId=e2e74b3f-b78d-46c7-a7ff-081ff888521f, totalOrdering=1}

We should add the catalog version (catalogEffectiveDate) as well, as this would be helpfu

MFlisar
MFlisar commented Feb 10, 2018

Bacause of following proguard config

-assumenosideeffects class org.solovyev.android.checkout.Check {
	static *;
}

I get following warnings:

Note: the configuration specifies that none of the methods of class 'org.solovyev.android.checkout.Check' have any side effects
Note: the configuration specifies that none of the methods of class 'org.solovyev.android.checkout.Check' have any
therefromhere
therefromhere commented May 1, 2020

Something based on https://docs.djangoproject.com/en/3.0/howto/upgrade-version/ would be a good idea.

  • Review the change log for breaking changes
  • Upgrade one feature release at a time (eg 2.2.x to 2.3.x)
  • Test for deprecation warnings before/after each feature release
  • Suggestion to run ./manage.py djstripe_sync_models after feature release in order to populate new fields - link to h
a-koka
a-koka commented Feb 8, 2020

@voltrue2 I think we should add some documentation for the validate method. I'm also happy to submit a PR for this. I'm receiving the following errors sometimes and it is unclear without investigating the code whether this means the request failed or if the receipt is invalid. In my particular case, both of these failures were for valid receipts.

{ Error: read ECONNRESET
    at TLSWrap.
oyeb
oyeb commented Dec 22, 2017

doctests will help us catch any stale examples in the documentation, in case the examples break due to changes in code.

The following need to be resolved for doctests to work:

  1. The outputs also have to be written down in the documentation
  • Typical response objects are huge (will take up a lot of space).
  • Responses are unique and can't be tested against.
  1. Our examples invoke calls
kinan53
kinan53 commented Jan 14, 2020

I saw this Project and this is very useful ! but the problem is that there is no guide anywhere which contains detailed instructions of How to install this on a localhost or on XAMPP !
that would be fantastic if someone can help me regarding this ! i see potential in this project.... please make it worth of your hard-work guys ! thanks !

evereq
evereq commented May 1, 2020

Similar to #798 (Activities) or #545 (Tags) we need to build generic feature Notes & Comments.

For each type of record (e.g. Contacts, Organizations, Employees, Invoices, etc), we should be able to add some notes which will be displayed in like timeline style (i.e. it's a list of notes, most recent notes at the top, oldest at bottom of the list). Note: it is possible that some entities already

Improve this page

Add a description, image, and links to the billing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the billing topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.