-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account: add publishable_key field #441
Conversation
Codecov Report
@@ Coverage Diff @@
## master #441 +/- ##
==========================================
+ Coverage 99.39% 99.39% +<.01%
==========================================
Files 34 34
Lines 1662 1663 +1
Branches 135 135
==========================================
+ Hits 1652 1653 +1
Misses 5 5
Partials 5 5
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #441 +/- ##
==========================================
+ Coverage 99.39% 99.39% +<.01%
==========================================
Files 34 34
Lines 1662 1663 +1
Branches 135 135
==========================================
+ Hits 1652 1653 +1
Misses 5 5
Partials 5 5
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #441 +/- ##
==========================================
+ Coverage 99.52% 99.52% +<.01%
==========================================
Files 34 34
Lines 1688 1690 +2
Branches 145 145
==========================================
+ Hits 1680 1682 +2
Misses 4 4
Partials 4 4
Continue to review full report at Codecov.
|
a5819aa
to
e6a0e07
Compare
Likely not needed - the ephemeral key seems to be enough after all. |
@blueyed are you able to update this branch against master and merge the migrations? If not I might punt this until the |
@paltman I would suggest waiting until the end of the week at least for the release. Otherwise it might become problematic with regard to migrations etc, in case there are changes that would need data migrations still. |
What happens this week? I have a follow-up milestone, Rosie, due at the end of November to capture any fixes after 4.0.0 (Samwise ships). There really isn't much left in this (Samwise) milestone. |
Tomorrow is a holiday in Germany, but then we will keep working on the integration. We have a mix of #400 / #402 in use (#440) for example, which makes sense to include IMHO. It might make sense to create a meta issue to track TODOs for the release, e.g. that migrations should be squashed (using Django's mechanism). |
IMHO there is no reason to rush a release with Stripe Connect integration that is still very bumpy. |
Fair enough. I relying on feedback from people actually using this feature in practice. I'm planning to build something with it for myself. I'm just getting nervous about how big this is becoming. I'll block any other non-connect related features until after the release. Do you want to create that issue with the TODOs and we'll add it to Samwise? |
Fixes #437.