-
Notifications
You must be signed in to change notification settings - Fork 812
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
Recurring Payments block - added example #13823
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: May 5, 2020. |
FYI @artpi in case you have spare cycles! |
Oh nice, I just discovered it and it's from October! Jeez, I must have seen it and forgot, sorry! |
This PR has been marked as stale. This happened because:
No further action is needed. But it's worth checking if this PR has clear testing instructions, is it up to date with master, and it is still valid. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation. |
c9e9a3b
to
a70075b
Compare
MichaelArestad, Your synced wpcom patch D34422-code has been updated. |
@MichaelArestad - thank you for this! Do you think there's a way to use another block (button) as a preview and just "fake it" ? |
There totally is, but it's a little over my head. |
Note to whoever takes this task:
|
I'll close this PR for now because of the lack of activity on this. We can always reopen in the future if needed, but it will need a rebase, so it may be easier to start a new PR at this point. |
Master issue: #13510
Adds example to Recurring Payments block
In progress notes
I don't believe the current preview is very good. In fact, no preview is better than this, however, this will get the conversation started.
When hovering over the block, you see a loading state where it tries to talk to Stripe:

When that fails, you see this:

Ideally, this is what we want the user to see:

I need someone like @gravityrail or an experienced JS dev to remove the notice and loading state for the preview so the button shows up instantly. Sadly, this is beyond what I'm comfortable with.
Changes proposed in this Pull Request:
Is this a new feature or does it add/remove features to an existing part of Jetpack?
Testing instructions:
Proposed changelog entry for your changes: