fix(stripe): remove price pushdown from subscriptions - #624
Merged
burmecia merged 1 commit intoAug 12, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix,
What is the current behavior?
The
priceparameter is listed as a pushdown filter forsubscriptions, but is missing from the table columns. Attempting to query or filter by it throws acolumn "price" does not existerror.What is the new behavior?
Removed
pricefrom thesubscriptionspushdown options and updated the docs.Since price is nested inside the
itemsarray and a subscription can have multiple items (a 1:n relationship), we chose to avoid mapping it to a single top-level column and instead remove it from the pushdown options.Additional context
This follows the discussion in #623.