Skip to content
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

Migrate rich billing portals to common billing portals #1796

Merged
merged 7 commits into from
Feb 22, 2024

Conversation

XaosSintez
Copy link
Contributor

@XaosSintez XaosSintez commented Feb 19, 2024

Summary

This PR removes rich billing portals and migrates its additional functionality to common billing portals

Checklist

  • Writing style
  • API design standards

description: ID of the plan.
maxLength: 50
example: plan_0YV7DENSVGDBW9S71XZNNYYQ0X
- $ref: ./SubscriptionOrderPlan.yaml
Copy link
Member

@adamaltman adamaltman Feb 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has these required props.

required:
  - name
  - currency
  - productId
  - pricing
  - recurringInterval

I don't understand why all of these are required and id prop.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this marked as resolved but nothing changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was changed. Now it's FlexiblePlan as I mentioned in Slack thread. So, you can send "id" only or full Plan content:
ddd1e50

@XaosSintez XaosSintez marked this pull request as ready for review February 21, 2024 10:52
@XaosSintez XaosSintez requested review from a team as code owners February 21, 2024 10:52
@XaosSintez XaosSintez merged commit 1dccfd9 into main Feb 22, 2024
2 checks passed
@XaosSintez XaosSintez deleted the billing-portal-migrate branch February 22, 2024 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants