Skip to content

Commit 72f8bc4

Browse files
authored
Add note about event type feature flags backwards compatibility (#259)
A user (+me and Tom) was recently confused about this
1 parent 948cd6a commit 72f8bc4

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

docs/event-types.mdx

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1176,10 +1176,14 @@ curl -X POST "https://api.us.svix.com/api/v1/event-type/user.signup/" \
11761176
</CodeTabs>
11771177

11781178
:::info[Important]
1179-
Keep in mind that endpoints with no event type filtering will receive all messages regardless of feature flags. Also, users with knowledge of a feature flag-gated event type can subscribe to that event type regardless of feature flags.
1180-
Feature flags only impact event types' visibility in the catalog and the API, not their deliverability.
1179+
Keep in mind that endpoints with no event type filtering will receive all messages regardless of feature flags.
1180+
1181+
Feature flags only impact event types' visibility in the app portal, catalog, and the API; not their deliverability. This means that endpoints with no event type filtering will receive all messages regardless of feature flags.
1182+
1183+
Additionally, if a user is subscribed to a feature flagged event, they will continue to be able to see it in the app portal regardless of whether the feature flag is enabled for them or not.
11811184
:::
11821185

1186+
11831187
## Appendix
11841188

11851189
### Generating an OpenAPI spec

0 commit comments

Comments
 (0)