-
Notifications
You must be signed in to change notification settings - Fork 525
Add endpoint to preview upcoming subscription charge including taxes #6867
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
Add endpoint to preview upcoming subscription charge including taxes #6867
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
📦 Next.js Bundle Analysis for webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 Fifty-eight Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sensible! Small logic caveats to fix :)
I'm wondering though if we could somehow find a way to factorize this logic with what we do in cycle, since it's basically the same thing. But that can be done later :)
|
|
||
| if subscription.status != "active": | ||
| ## FIXME Is a 404 the correct behavior? | ||
| raise ResourceNotFound() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could indeed define a specific 400 error, but not a big deal
20d71fb to
50e94c1
Compare
| if subscription.discount.is_repetition_expired( | ||
| subscription.started_at, subscription.current_period_start | ||
| ): | ||
| subscription.discount = None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we assign discount as a local variable? It's a bit scary like this 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, yeah, good call, I copied this over without thinking too much, sorry.
cb69dde to
d8379aa
Compare
Issues attributed to commits in this pull requestThis pull request was merged and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |

Related to #6357
polar-preview-including-taxes.mp4