Skip to content

Adds support for product marketing_features field#134

Merged
kevcodez merged 3 commits intostripe:mainfrom
vinagrito:product-marketing-features-field
May 23, 2025
Merged

Adds support for product marketing_features field#134
kevcodez merged 3 commits intostripe:mainfrom
vinagrito:product-marketing-features-field

Conversation

@vinagrito
Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Adds support for the marketing_features field under the Stripe product entity

What is the current behavior?

the attribute is missing from the schema

What is the new behavior?

The new field would be parsed from the webhook event

Copy link
Copy Markdown
Collaborator

@kevcodez kevcodez left a comment

Choose a reason for hiding this comment

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

@vinagrito
Copy link
Copy Markdown
Contributor Author

stripe-sync-engine/src/schemas/product.ts

Added the one missing 👍
(I can see it is already part of the product schema)

@kevcodez kevcodez merged commit eef33c3 into stripe:main May 23, 2025
2 checks passed
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 0.33.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

tonyxiao pushed a commit that referenced this pull request Apr 15, 2026
Calling validateProject failed on branch projects because the /projects api
doesn't return branch projects. While it was possible to get branch projects by
getting other api endpoints, it's needlessly complex to just verify if a project
exists or not. Intead we omit this call and let the other api calls fail during
installation if the project doesn't exist or there are permission issues.
Ideally we'd have a token introspection api which can tell us which permissions
the current token has, but we don't have such an api endpoint exposed currently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants